Media fixes – Vivaldi Browser snapshot 2920.4
-
@iAN-CooG said in Media fixes – Vivaldi Browser snapshot 2920.4:
SupportPartitionedBlobUrl
Interesting to read this source comment about that
https://chromium.googlesource.com/chromium/src/+/HEAD/net/base/features.cc// Whether to use the new code paths needed to support partitioning Blob URLs. // This exists as a kill-switch in case an issue is identified with the Blob // URL implementation that causes breakage. // TODO(https://crbug.com/1407944): Kill-switch activated - investigate cause of // increased renderer hangs. BASE_FEATURE(kSupportPartitionedBlobUrl, "SupportPartitionedBlobUrl", base::FEATURE_DISABLED_BY_DEFAULT);
Yeah, an issue is identified with the Blob, it's found, literally everywhere
They released this without even testing. -
@iAN-CooG So sounds like I should add Vivaldi Stable to the update ignore list for now then.
-
@LocutusOfBorg said in Media fixes – Vivaldi Browser snapshot 2920.4:
I'll happily put Vivaldi itself on the ignore list
-
@iAN-CooG from what you posted sounds like a screw up on Chromes end so all we can do is wait for a fix from them or the Vivaldi devs. Now how does this affect Chrome itself, Brave, Opera, etc.......?
-
@iAN-CooG Once again, Vivaldi Snapshot testers are crash test dummies for Chromium experimentation!
But now, I have learned more about what web BLOBs are!
-
@Ruarí Stable 5.7 when?
-
Regarding SupportPartitionedBlobUrl, a bit of background: I have already re-enabled the feature in internal builds (will be in next snapshot), and we are planning to fix the patch that broke (it depended on the feature being enabled, raw Chromium was not affected).
A potential problem with re-enabling the feature is that the reason upstream disabled it is that the feature was associated with an significant increase in some kind of crash/hangs (the report is not public), so re-enabling it may lead to a bit of instability until upstream discover what caused the issue and fixes it.
The feature was disabled by upstream in the update we did on Monday, and this snapshot was released the day after.
While we had indications about new media issues, those might have been related to certain other changes we did recently (and which did cause one of the problems in the previous snapshot); we had only associated the issue with an image paste issue until @Pathduck noticed the use of bloburls on one of the sites having issues.
-
The previous snapshot broke video acceleration on my KDE Neon, it is still broken in this snapshot.
Had to go back again to the January 9th snapshot. -
@Panino Downgrading is never recommended. It can mess up your profile.
Install the Stable version and use that if it works on your hardware. Install the Snapshots as a Standalone version for testing purposes.
Install the Snapshot as a Standalone Version so that it does not interfere with your settings for the Stable release.
I use a Standalone version of the latest Snapshot, and use it as my default browser - most bugs don't stop me from browsing. I install the latest Stable for all users with its default settings for comparison purposes.
-
We have another Snapshot for your desktops. Go check it out!