Youtube / Twitch / Twitter videos not playing + crash issues
Hi folks. I run Vivaldi v1.10.867.42 on two computers:
- a MacBook Pro 2011, running macOS 10.12.4
- an iMac 27'' mid-2010, running macOS 10.12.4
- Twitter: videos go black and say "The media could not be played".
- Youtube / Twitch: some videos either load indefinitely or say "An error occured. Please try again later."
- Twitch: videos load indefinitely without any signs of buffering.
MacBook Pro: Facebook crashes the browser shortly after it fully loads its assets or just by scrolling through the Home page.
Could this be a Flash / HTML5 problem? Any help would be greatly appreciated, as I just switched to Vivaldi and really do not want to go back to Chrome. Thank you ~
@deusnovus It's likely that the GPU on your system has been blacklisted by the Chromium developers.
Could you please try the following:
Go to vivaldi://flags and Enable the "Override software rendering list" flag; it's the first entry on the page. Then hit the Relaunch button at the bottom of the page. This should enable the videos to play and could stop the crash from occurring as well.
Is the crash on your MacBook Pro occurring on a public Facebook page? If so, I know the developers are looking for a way to replicate a similar crash that I reported, but are having difficulties doing so on their macOS 10.12 systems.
@xyzzy Yes, this was it! Thank you so much, you've been so helpful! Would there be a case where I would have to re-enable this option?
@deusnovus This is one of the safer flags to enable but it's possible that you might encounter some rendering glitches or performance issues on some web sites.
The real fix is for the developers to find a way to make Vivaldi function equally well both with and without GPU hardware acceleration.
If you happen to have a URL that you can share that crashes Vivaldi on macOS Sierra, I'm sure the developers would really appreciate it.
@xyzzy Absolutely, I'd be more than happy to share any Vivaldi crash reports with the team. Once again, thank you so much!
@deusnovus You're most welcome. I'm glad the tip worked out for you!
You can file a bug report for the crash at https://vivaldi.com/bugreport/ along with the URL that triggered it.
Just curious... if you look at the crash report in Console.app... look for a line toward the top of the report that says Crashed Thread... did Vivaldi crash for you in Chrome_IOThread?
@xyzzy I will, next time I encounter a crash! And yes, Vivaldi crashed in Chrome_IOThread!
Just in: disabling the "Override software rendering list" flag doesn't seem to work on my iMac 27'', it only worked on my MacBook Pro...
@xyzzy I apologize for the double post, but I was wondering whether you have any suggestions on fixing the same problem on an iMac 27''!
@deusnovus Hi. Sorry... the tips I shared here came from troubleshooting the same issues and crashes on my own MacBook Pro. Clearly, with the ATI Radeon HD 5000-series GPU in your iMac, Vivaldi is using a different code path that I can't trace. I'm also just a volunteer here, so I don't have access to internal resources, contacts, or tools that the internal testers may have at their disposal.
The best that I can do at this time is to rummage through the Chromium team's bug tracker to see what they might have done to "break" Vivaldi on your system. I'll let you know if I find anything at all. Until then, regrettably, I'm totally at a loss of ideas.
@xyzzy Oh, I hear you... I will also try to do some research and ask around. It's worth mentioning I had similar problems with Chrome + iMac too. (the videos would play, but some wouldn't have any sound) But since they have identical architecture, it makes sense. Thank you so much regardless!
@xyzzy Thank you for this solution! Why are Chromium devs blacklisting GPUs? Less-than-total compatibility with what they're trying to do?
It would give Vivaldi an advantage over vanilla Chrome(-ium) it it were able to detect when it is crashing for this reason, and enable this flag on its own.
@aratuk I'm glad that things are working better for you now.
Re: the GPU blacklist, I'll try to summarize the situation as best as I can... The GPU drivers are actually blacklisted in Chrome and Chromium as well. The Chromium developers are currently making some optimizations to their GPU software stack and (most likely) found that their changes had caused some performance and/or rendering issues with some hardware... so they disabled GPU hardware acceleration by blacklisting the driver. This is not a big deal in Chrome because it was built with codecs that work with software-based rendering. However, Vivaldi was not built with any patent-encumbered codecs and relies on the operating system's libraries to provide the necessary support... but on macOS, this solution currently works only when hardware acceleration is enabled. Another bug was causing the crash you experienced. Vivaldi is essentially using a software build configuration that Google had not tested and the Vivaldi developers now have to come up with an appropriate fix.