Open LOFer opened 7 years ago
"Aw, Snap!" have multiple error codes, which one are you getting? https://support.google.com/chrome/answer/95669
All of them are related to network in one way or the other.
The cache is sorted in:
/home/pi/.config/chromium/Default/Application Cache
/home/pi/.config/chromium/Default/Storage/ext/chrome-signin/def/Cache
/home/pi/.config/chromium/Default/Storage/ext/chrome-signin/def/GPUCache
/home/pi/.config/chromium/Default/GPUCache
/home/pi/.config/chromium/Default/History Provider Cache
/home/pi/.config/chromium/Default/Service Worker/CacheStorage
/home/pi/.config/chromium/Default/Service Worker/ScriptCache
/home/pi/.config/chromium/ShaderCache
/home/pi/.config/chromium/ShaderCache/GPUCache
Same problem!
Using new FullPageOS RC1 and when run Youtube Video "Aw Snap"
Any fix?
@pablosouza10 that's a different issue, see #29 webm and flash videos should work. But mp4 is a problem. Also upvote this :) http://raspberrypi.stackexchange.com/questions/59524/chromium-tab-crashes-if-mp4-video-with-gpu-acceleration
@guysoft , Tks. Now I'm try New Raspbian Pixel, Youtube's hd videos running so much better w/ no modification. Waiting for fix FullPageOs.
@pablosouza10 Ok I think I understand what they did in Pixel. Pixel comes default WITHOUT GPU accleration. However, it comes per-installed with the h264ify extension. So you can either have GPU enabled and have accelerated canvas. Or disable the GPU and have h264ify decode youtube videos. Also see https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=157049.
Update: confirmed. If you want to play youtube videos:
sudo raspi-config
advanced options
GL driver
legacy
ctrl-t
Closing if no reply
@guysoft Raspberry Pi forum lists a few workarounds for the accelaration problem. Do you think any of them can temporarily solve the problem of accelarated video playback until this issue is taken care of by Raspbian?
clear_uniforms_before_first_program_use (I guess this is a Chromium flag?)
Cheers, Tailor
@tailorvj Can you please link to a specific solution? I gave a pretty solid one two comments back.
LOVE this project - thanks so much for it!!!
I am running this on our school reception TV and it has been going fine for a month (staff and parents love it!!) but recently, a few times a day we now get the white screen of doom with the "Aww Snap" message.
The web server is running fine and network connectivity is not a problem as I can connect from another machine so it is something to do with the local (to the Pi) instance of Chromium that is running.
Anyone had this before - how can I fix this? Is it a cache issue and if so, where is the cache stored for this?
Cheers!