![]() ![]() And yet, there are no crash reports from 39 or 40 prior to release, and no crashes in 39 or 40 with a build id matching any of our official releases. This bug was first filed against Firefox 34, but there's been a huge spike with the 40 release. ![]() It looks like this is specific to gstreamer-1.0, Ubuntu or both. Is it possible to see from the crash reports whether hardware acceleration is on? Safwam's system also seems to have Intel graphics when looking at the report. It might have been that I changed the settings and forced hardware acceleration on that solved my issues. I had already tried disabling hardware acceleration which didn't seem to help, but then I saw on the about:support page that my old Intel graphics processor was blacklisted. On the Ubuntu system were I experienced crashes I managed to stop it from crashing by changing Firefox settings. ![]() Maybe it's related to this:Ĭhecking my crashes page, it doesn't show anything for my Linux Mint installation, so it might only have been the CPU usage issue I had. On closer recollection, maybe uninstalling libtotem-mozilla only solved the CPU usage issue. I think originally I was having trouble with both crashes and high CPU usage. Ok, I might have mixed up two unrelated issues then. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |