There are errors in your #0317 logs. I would suggest starting with a fresh .kodi when booting #0317, as there is either database corruption or incompatible addons. Rename your existing .kodi folder if you want to restore it later. Enabling debug log (specifically, CEC component logging) might also shed some light on the problem if it continues with a fresh .kodi.
(2015-03-18, 15:05)popcornmix Wrote: [ -> ]You seem to have upgraded to a very old build:
Not sure why he did it that way, but there are four logs in one pastebin - two very old, two of #0317 (at the bottom).
@zaphod24/@afremont: I've uploaded debug builds which might produce a more useful crash log. Please also enable debug logging (either via the GUI, or add <loglevel>2</loglevel> to as.xml) as this might give more information about what is happening at the time of the crash.
You'll need to ensure your FAT partition is at least 378MB as the debug-enabled SYSTEM image is quite large (262MB).
#0318x::
RPi /
RPi2
Could be wrong, but I think maybe I'm boned with the default partitions:
/dev/mmcblk0p1 261868 103368 158500 39% /flash
Looks to me like it's only 260meg...
@zaphod24: Yep. If you can, resize the partitions using gparted (and a Linux PC, or LiveCD). You may also then need to reformat the FAT partition with FAT32 partition in order to use the extra space if it's been formatted with FAT16.
(2015-03-18, 03:05)zaphod24 Wrote: [ -> ]Slightly different error (not missing fields this time) but Kodi is still crashing regularly with 0317. I even completely deleted the EPG database and restarted to let it build it from scratch. Crash log at http://sprunge.us/ZSGO
I do have the same problem. Crash after read epg database.
http://pastebin.com/HAxgaJzp
If you can, please try the #0318x debug-enabled build as the crash logs from regular builds don't include any useful information for this particular crash.
Is this related to a similar problem arising in pvr.mythtv recently where there was a memory leak on getting EPG data resulting in a crash? There were some details on the main pvr.mythtv thread. If you think this might be related I can search out the forum posts.
(Just a wild guess here)
(2015-03-18, 15:05)popcornmix Wrote: [ -> ] (2015-03-18, 15:01)vbaros Wrote: [ -> ]I just upgraded from pre-Isengard to a latest #0317 build.
...
Here is the full kodi.log:
http://pastebin.com/HFSEcsLu
You seem to have upgraded to a very old build:
Code:
19:13:37 19.021235 T:3058982912 NOTICE: Kodi compiled Oct 3 2014 by GCC 4.9.1 for Linux ARM 32-bit version 3.16.3 (200707)
19:13:37 19.023943 T:3058982912 NOTICE: Running on OpenELEC (Milhouse) - Version: devel-20141003033024-r19322-gdded97b 5.0, kernel: Linux ARM 32-bit version 3.16.3
...
Raspberry PI firmware version: Oct 1 2014
I definitely upgraded to the latest version. I just did the standard 4 files update. I'm not sure why there were old logs in the latest .zip.
If you scroll down you can find the log from today at 12:32:28 where the problem started.
(2015-03-18, 22:12)nickr Wrote: [ -> ]Is this related to a similar problem arising in pvr.mythtv recently where there was a memory leak on getting EPG data resulting in a crash? There were some details on the main pvr.mythtv thread. If you think this might be related I can search out the forum posts.
(Just a wild guess here)
Not sure, we seem to have the same crash with Myth and WMC. Would be great to get the insight of any Myth or WMC developers.
(2015-03-18, 22:23)Milhouse Wrote: [ -> ] (2015-03-18, 22:12)nickr Wrote: [ -> ]Is this related to a similar problem arising in pvr.mythtv recently where there was a memory leak on getting EPG data resulting in a crash? There were some details on the main pvr.mythtv thread. If you think this might be related I can search out the forum posts.
(Just a wild guess here)
Not sure, we seem to have the same crash with Myth and WMC. Would be great to get the insight of any Myth or WMC developers.
This is the post I was thinking of
http://forum.kodi.tv/showthread.php?tid=...pid1859434
Dunno if it leads to anything helpful!
Noob question as I've never had a Pi. Just got my Pi2. How do I set-up microSD card with latest build on p1 of this thread? I want OpenELEC; don't need other OS.
(2015-03-18, 21:24)zaphod24 Wrote: [ -> ]Could be wrong, but I think maybe I'm boned with the default partitions:
/dev/mmcblk0p1 261868 103368 158500 39% /flash
Looks to me like it's only 260meg...
I can't test mine yet since the wife is using the TV, but I modified the create_sdcard script. I changed the first parted command to create the partition 378MiB and the second one to 380 to make the number modulo 4. That seemed to do it, but I have to boot it before I'll know.
Of course that wipes out everything on the card, but I don't mind setting it back up since it's not that difficult to do.
http://paste.debian.net/161994/
Like I said, I haven't tested this just yet, but I don't see why it won't work. The default sizes definitely don't work. And one more time,
this will wipe the flash card, so don't use one that has data you want to keep.
EDIT: Be careful running this script as it could wipe out your Pi's sdcard if you get it wrong. I put my new sdcard in a USB adapter and plugged it into my raspbian Pi (B+) and it shows as /dev/sda. Therefore the command to write to the card is:
sudo create_sdcard /dev/sda