rabzu
commented
5 years ago Any news on this?
Open ilyai opened 5 years ago
rabzu
commented
5 years ago Any news on this?
guysoft
commented
5 years ago Hey, I would need a webpage to test against.
You could uncomment the auto refresh on crash script that is in start_chromium_browser
ilyai
commented
5 years ago Actually I was able to reproduce this with playing youtube videos only.
I set fullpageos.txt to https://www.youtube.com/watch?v=Pkh8UtuejGw&list=PLFgquLnL59alCl_2TQvOiD5Vgm1hCaGSI, switched to fullscreen and let youtube autoplay videos.
It has been playing for almost 2 hours, but memory was keep growing:
And finally chrome tab crashed.
The last message before the tab was killed:
[675:738:0806/162008.827460:WARNING:audio_sync_reader.cc(187)] ASR: No room in socket buffer.: Broken pipe (32)
Full browser's log: chrome_debug.log
ilyai
commented
5 years ago Regarding crash script (/home/pi/scripts/start_chromium_browser) I commented two lines according to the instruction but it didn't seem to be working:
# Standard behavior - runs chrome
#chromium-browser --kiosk --touch-events=enabled --disable-pinch --noerrdialogs --disable-session-crashed-bubble --app=$(head -n 1 /boot/fullpageos.txt | sed -e "s/{serial}/${SERIAL}/g")
#exit;
# Remove the two lines above to enable signage mode - refresh the browser whenever errors are seen in log
BasilHall
commented
5 years ago I can confirm that I have experienced something similar on another Raspbian based Kiosk OS distro with this version of Chromium. We saw it when playing our own internal web page with simple HTML5 Video tags and H264 content on a RPi 3. The video could loop for around 30-45 minutes and then the Chromium tab would crash (and sometimes all of Chromium).
Much like FullPageOS, we had enabled hardware video acceleration in Chromium (overriding the GPU blacklist), and I wonder if this had an effect on things.
I say this to point out that this may be a Chromium issue common to all the Raspbian based distros. I am in the process of migrating our main Kiosk image over to FullPageOS and will retest the issue again and report back.
ilyai
commented
5 years ago @BasilHall I tried testing with --disable-accelerated-video-decode option enabled but nothing changed, Chromium tab crashed as usual.
guysoft
commented
5 years ago You can also try the no-acceleration variant.
ilyai
commented
5 years ago @guysoft I tested no-acceleration version (2019-06-20-fullpageos-no-acceleration-buster-lite-0.11.0.img) and it worked only on RPi 3, and not on RPi 4. On the later it just booted up and showed a grey screen, no chromium or mouse cursor.
guysoft
commented
5 years ago @ilyai Sounds like something has changed with the video memory, I will have to test when I get to it, unless you want to.
The difference between the acceleration and no-acceleration is:
echo "gpu_mem=128" >> /boot/config.txtlocated at: https://github.com/guysoft/CustomPiOS/blob/devel/src/modules/gui/start_chroot_script#L39
BasilHall
commented
5 years ago @ilyai You might want to try removing the following flag from Chromium's startup and see if this issue still persists: "--ignore-gpu-blacklist" This will disable a significant portion of the GPU's acceleration in Chromium, but it would be informative to see if the crash still happens or not. This would help us figure out if it is a video driver instability issue in Chromium, or just a more general issue in this version of Chromium in Raspbian.
ilyai
commented
5 years ago @BasilHall I tested with this option (added in /etc/chromium-browser/default) there was no difference. Is there anything else I can try?
guysoft
commented
5 years ago You can try reporting the bug to chromium, I can't see how we can fix it on our end.
ilyai
commented
5 years ago @guysoft Most likely this is due to this bug ( https://bugs.chromium.org/p/chromium/issues/detail?id=969049 ) which is reproducible in v74, the one FullPageOS has, and was fixed in more recent versions of Chromium. So updating Chromium package within FullPageOS should fix this.
guysoft
commented
5 years ago @ilyai Good catch. I guess this means that just restarting on a crash is the only workaround we can do at the moment.
ilyai
commented
5 years ago @guysoft And updating Chromium package to v76 (current) in FullPageOS image isn't planned?
guysoft
commented
5 years ago The Rpi foundation added a Debian package, but they did not update the base image. I guess we could add to the build a stage that updates chromium.
kleintorres
commented
4 years ago Has this been resolved? We plan to use FullPageOS for a Kiosk showing some videos and every distro has the same problem with Chromium
guysoft
commented
4 years ago @kleintorres There are three workarounds that AFAIK fixes all issues I ever encountered. You might not need any of them, it depends on the usage you have with Chromium.
I have dashboards running for days here.
I'm running a Chrome app on Raspberry Pi 3 and 4 that plays media content using HTML5 (video, images, web widgets) and after some time the web page crashes (Aw, Snap! error is displayed). System log contains the following:
FullPageOS version: 0.11.0
Screenshot of htop running just before the crash:
And the one after it:
I also tried to take memory heap snapshots using Chrome Inspector and they where not much different in size, i.e. heap was not growing.