That post seems to suggest an out of memory issue,but I didn’t see that in @makk509’s log nor my own testing. I will try it with the latest kernel and userland on Sunday.
Thanks Sam.
Update
I’ve updated my system using the May release but the problem remains. I’ve tried several things to identify the issue.
- Created a new folder and copied different files from the same collection to it. I only copied 2 files so it’s definitely not the number of files in the folder. I called the folder A1 and the files 1.jpg and 2.jpg to ensure it wasn’t a file length or naming issue.
- Copied the same folder from my USB HD to the Vero home/pictures/ location to ensure it wasn’t a disc error.
In all cases I get the same failure. I can view every image in a collection if I exit back to the thumbnails screen before selecting the next image but as soon as I try to move directly from one full screen image to the next, the system freezes, black screens and reboots. The effect appears to be immediate as nothing ever gets written to the log files.
I browsed through several of my previous image collections to check if the issue was caused when I uploaded this new collection. Interestingly I’ve found that several of my old collections still function correctly but several which used to work OK are now failing as above. I can’t find any common theme, file size, file type, meta data. Nothing stands out.
I’m all out of ideas. So any suggestions would be very welcome.
In the absence of any other ideas, does anyone think it’s worth me trying something major like re-imaging my SD card? I’m grasping at straws here but I’m out of ideas.
Decided to start from scratch today. Got a new SD card. Downloaded a new image. Ran the OSMC updates to get to the latest may release. At this point I had a completely clean build. No external drive connected, no addons installed.
I copied 2 images to a new directory on the SD card /home/OSMC/Pictures and I still have exactly the same behaviour. I can view either image if I select it from the thumbnails but if I have an image open i.e view and image full screen and I press either the left or right navigation keys to move to the next image, the system freezes and reboots.
I’ve eliminated memory issues either from file size or number of images in a folder and I’ve eliminated corrupt images. Other than a bug I’m not sure what’s left??
As you only have two pictures can you upload them somewhere so we can try on our systems?
I’ve sent you a dropbox link
Ok will try and let you know
Thanks fzinken.
I have copied the two pictures into /home/osmc/Pictures added the folder to pictures and browsed trhu them with multiple left/right/left combinations and was not able to reproduce your crash.
Are you having the same crash when playing them in slideshow (press spacebar)?
not sure what you mean by spacebar fzinken, I’m viewing in these on my vero and controlling it with my TV remote so know keyboard but if I select slideshow from the left hand, slide out menu, yes, the same thing happens, the first image loads then when the slideshow tries to move to the next image I get a black screen and a reboot. I’ve tried this with several different images from the collection so I don’t think it relates to a specific image problem.
I’m starting to worry that the Vero has developed a fault as nobody seems to be able to reproduce the error but I’m getting the error constantly even as I mentioned, on a brand new image with no customisation of any sort.
Well maybe you ask @sam_nazarko to try once more to replicate the issue and maybe provide debug logs with the new setup and showing the crash (while it might happen so fast that nothing can be written to the files. Maybe have two SSH session running one with tail -f /home/osmc/.kodi/temp/kodi.log and one with sudo journalctl -f and check if any of them record something when the crash happens.
Thanks fzinken, Sam’s just DM’d me to say he’s looking in to it. For what it’s worth (and I’ve just said this to Sam) I’ve just tried resizing the images, reducing them from 4mg to about 0.5meg and the problem goes away. I created a folder with 4 images in it, the original 2 and the same 2 images reduced in size. I can navigate the smaller 2 without any problem but as soon as I load one of the larger files and try to navigate off, the system reboots.
I tailed the kodi.log file as you suggested but it doesn’t seem to show anything. See below. The log shows me open the 1st small file, move to the 2nd small file, move to the 1st large file and the log end as soon as I try to move to the 2nd large file.
15:04:50 T:1757451248 DEBUG: PushCecKeypress - received key b duration 227
15:04:50 T:1956835328 DEBUG: ------ Window Deinit (MyPics.xml) ------
15:04:50 T:1956835328 DEBUG: ------ Window Init (SlideShow.xml) ------
15:04:50 T:1956835328 INFO: Loading skin file: SlideShow.xml, load type: KEEP_IN_MEMORY
15:04:50 T:1956835328 DEBUG: Loading the current image 0: /media/Seagate Expansion Drive/Pictures/BVI 2016 10/A20160420_091946 (800x450).jpg
15:04:50 T:1423000560 DEBUG: Thread BgPicLoader start, auto delete: false
15:04:50 T:1423000560 DEBUG: Finished background loading slot 0, 0: /media/Seagate Expansion Drive/Pictures/BVI 2016 10/A20160420_091946 (800x450).jpg
15:04:50 T:1956835328 DEBUG: Loading the next image 1: /media/Seagate Expansion Drive/Pictures/BVI 2016 10/B20160420_102832_002 (800x450).jpg
15:04:50 T:1423000560 DEBUG: Finished background loading slot 1, 1: /media/Seagate Expansion Drive/Pictures/BVI 2016 10/B20160420_102832_002 (800x450).jpg
15:05:04 T:1599140848 DEBUG: Thread JobWorker 1599140848 terminating (autodelete)
15:05:04 T:1414591472 DEBUG: Thread JobWorker 1414591472 terminating (autodelete)
15:05:04 T:1515254768 DEBUG: Thread JobWorker 1515254768 terminating (autodelete)
15:05:04 T:1616614384 DEBUG: Thread JobWorker 1616614384 terminating (autodelete)
15:05:16 T:1667732464 DEBUG: script.module.osmcsetting.updates : - blurp 896 - SlideShow.xml
15:05:20 T:1757451248 DEBUG: PushCecKeypress - received key a8 duration 0
15:05:20 T:1956835328 DEBUG: SECTION:UnloadDelayed(DLL: special://xbmcbin/system/ImageLib-arm.so)
15:05:20 T:1956835328 DEBUG: OnKey: 168 (0xa8) pressed, action is Right
15:05:20 T:1956835328 DEBUG: Starting immediate transistion due to user wanting slide /media/Seagate Expansion Drive/Pictures/BVI 2016 10/B20160420_102832_002 (800x450).jpg
15:05:20 T:1757451248 DEBUG: PushCecKeypress - received key a8 duration 228
15:05:21 T:1956835328 DEBUG: Image /media/Seagate Expansion Drive/Pictures/BVI 2016 10/A20160420_091946 (800x450).jpg is finished rendering, switching to /media/Seagate Expansion Drive/Pictures/BVI 2016 10/B20160420_102832_002 (800x450).jpg
15:05:21 T:1956835328 DEBUG: CAnnouncementManager - Announcement: OnPlay from xbmc
15:05:21 T:1956835328 DEBUG: GOT ANNOUNCEMENT, type: 1, from xbmc, message OnPlay
15:05:21 T:1956835328 DEBUG: UPnP: Building didl for object ‘’
15:05:21 T:1956835328 DEBUG: Loading the next image 2: /media/Seagate Expansion Drive/Pictures/BVI 2016 10/C20160420_091946.jpg
15:05:22 T:1423000560 DEBUG: Finished background loading slot 0, 2: /media/Seagate Expansion Drive/Pictures/BVI 2016 10/C20160420_091946.jpg
15:05:32 T:1757451248 DEBUG: PushCecKeypress - received key a8 duration 0
15:05:32 T:1956835328 DEBUG: OnKey: 168 (0xa8) pressed, action is Right
15:05:32 T:1956835328 DEBUG: Starting immediate transistion due to user wanting slide /media/Seagate Expansion Drive/Pictures/BVI 2016 10/C20160420_091946.jpg
15:05:32 T:1757451248 DEBUG: PushCecKeypress - received key a8 duration 226
15:05:33 T:1956835328 DEBUG: Image /media/Seagate Expansion Drive/Pictures/BVI 2016 10/B20160420_102832_002 (800x450).jpg is finished rendering, switching to /media/Seagate Expansion Drive/Pictures/BVI 2016 10/C20160420_091946.jpg
15:05:33 T:1956835328 DEBUG: CAnnouncementManager - Announcement: OnPlay from xbmc
15:05:33 T:1956835328 DEBUG: GOT ANNOUNCEMENT, type: 1, from xbmc, message OnPlay
15:05:33 T:1956835328 DEBUG: UPnP: Building didl for object ‘’
15:05:33 T:1956835328 DEBUG: Loading the next image 3: /media/Seagate Expansion Drive/Pictures/BVI 2016 10/D20160420_102832_002.jpg
15:05:35 T:1423000560 DEBUG: Finished background loading slot 1, 3: /media/Seagate Expansion Drive/Pictures/BVI 2016 10/D20160420_102832_002.jpg
15:05:59 T:1757451248 DEBUG: PushCecKeypress - received key a8 duration 0
15:05:59 T:1956835328 DEBUG: OnKey: 168 (0xa8) pressed, action is Right
15:05:59 T:1956835328 DEBUG: Starting immediate transistion due to user wanting slide /media/Seagate Expansion Drive/Pictures/BVI 2016 10/D20160420_102832_002.jpg
15:05:59 T:1757451248 DEBUG: PushCecKeypress - received key a8 duration 227
So nothing in the other window with the journalctl when it crashes?
Also wondering about the " UPnP: Building didl for object ‘’"
Are you accesing OSMC via UPNP at the same time? Maybe try to disable UPNP to see if it makes a difference.
No nothing in the journal. There’s nothing running on OSMC at the moment and I’m just using the TV remote to control it, so no UPNP devices. I’ll disable it and check though.
Nope. Same result. The UPnP entry has disappeared but other than that the log is identical and the behaviour was exactly the same.