Videos won't play in Twitter, 6.1.3035.111 (RESOLVED)

[irritable]

Vivaldi 6.1.3035.111 (Stable channel) (64-bit)
Revision b2568a9aaecd4a7793d10fa7b389233a3b18bee8
OS Linux
JavaScript V8 11.4.183.25
User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36
.........................................................

I'm unable to play videos in Twitter with the latest version of Vivaldi: "Unable to play video".

At the same time, the Twitter tab becomes slow and eventually unresponsive & the processor usage climbs, as does memory usage for the tab.

Closing the whole browser & restarting it clears the memory/processor issue but not the video problem.

I created a new user data directory & ran without any extensions (so a completely new install essentially) and got the same result.

Note that update-ffmpeg reports that no updates are needed.

If I run up previous versions I had installed (6.1.3035.100, 6.1.3035.84) these work perfectly.

I haven't tried a snapshot version yet.

[DoctorG]

@irritable Close Vivaldi
Try in shell: sudo /opt/vivaldi/update-ffmpeg
In Vivaldi check if you have enabled Settings → Webpages → Use of Hardware Acceleration ; if not then enable and restart.
In vivaldi://components page check Widevine "Content Decryption Module" section and hit Check for Update button below.

I can not test Twitter.
Perhaps it is a extension you use.
Just for a short test, start vivaldi --disable-extensions and chekc Twitter video again.

[irritable]

@DoctorG

OK but I stated clearly in my post that I had tested this with a brand new install with no extensions loaded, that I'd run update-ffmpeg, and as this is the 64bit Linux, Widevine is not needed (though to be fair I did not mention that)

[DoctorG]

@irritable Sorry i missed your changed post.

What is show in vivaldi://gpu?
Please copy and paste here with </> button.

[irritable]

@DoctorG

Bizarrely, I have changed nothing else since my last post, and videos now work again this morning.

So, I suspect that this was a Twitter problem and not a Vivaldi problem.

Given that Musk has fired every engineer who had a clue, and that the entire site is daily ever more unstable, this isn't surprising.

this can be treated as resolved without further need for suggestions, I think.

[DoctorG]

@irritable Nice to read that all is solved for you