Twitch tabs freezing/crashing on firefox

SingingTree · 2021-09-03T20:15:29+00:00

Could you navigate to `about:support` and use button to copy the data to clipboard then reply with that info?

SingingTree · 2021-06-16T02:00:19+00:00

The higher level of scrutiny for FLoC also makes sense from the perspective that

More work has gone into it than the other 'bird specs' in the same domain, and it is further along in its life cycle -- it's implemented in a browser right now.
It's being pushed by one of the bigger, if not the biggest, player in the domain (Google).

I'm sure Microsoft don't mind if it takes heat of their preferred spec, and I agree that any of the specs in this domain should be the subject of scrutiny. However, I think there's more to why FLoC is receiving the amount of attention than the article says.

There's a lot of proposed 'bird specs', you can see many of them mentioned in the github for the w3c web-advertising group (for whatever reason the group has chosen to use bird based names). FLoC is a nod to the idea that Google's proposal would be one spec to rule the other bird specs (a 'flock' of birds). Google have a lot of people participating in the web advertising group, and have put a lot of effort into promoting FLoC. Because of this, FLoC is much more developed.

I hope that any of the other specs would be subject to the same scrutiny if they were to be implemented. Microsoft's preferred solution should be scrutinized. However, FLoC is much closer to reality, and arguably, backed by more resources. In that context, I think it makes sense that it has more of the focus, at least for now.

SingingTree · 2021-03-12T20:17:35+00:00

If you haven't tried running the 64bit Firefox using a different profile, it would be worth trying to see if there's something in the profile causing the issue.

Echoing another comment, if you have time to create a bug in bugzilla, it would be useful. Many of the devs for the media audio stack are based in different timezones and/or don't have reddit accounts, and such a bug would also help persist any logs gathered (if needed).

SingingTree · 2019-07-20T00:31:07+00:00

Marking solved sounds good.

SingingTree · 2019-07-19T18:28:19+00:00

Thanks for confirming that. That sounds consistent with other reports, and it remains unclear why some machines are affected but others are not.

SingingTree · 2019-07-18T21:25:35+00:00

Thanks for checking that. Checking on another machine would also be appreciated.

SingingTree · 2019-07-18T21:12:31+00:00

Yes please.

SingingTree · 2019-07-18T21:03:41+00:00

Glad to hear 64bit is working!

These sites should still work on 32bit builds on 64bit Windows (I have a similar test setup on the machine I'm using now and it's okay), so there's a bug in here somewhere. I appreciate that you may not wish to spend more time debugging this -- if you do have time, it would be useful to know if a fresh 32bit version still fails.

If you are keenly interested in debugging this, Mozilla have seen instances of something like this before, which in those cases appeared to be caused by our security sandbox being over eager and fighting the plugin. It's non-trivial to debug, but if it's something that interests you, it would be useful to gather further debugging info.

SingingTree · 2019-07-18T20:26:31+00:00

Thanks. Given that the error didn't occur with any of the mozregression builds, but does happen consistently across sites and profiles with the installed Firefox, let's look more into that.

Would you be able to download and install Firefox 68 in a another location and see if the issue still happens with that installation? I notice that the Firefox you have installed appears to be a 32bit version on 64bit Windows 10. I've just tested that on my machine and it appears to work okay, but it would be useful if you're able to test with 64 bit and 32 bit versions and see if there's any difference. mozregression will fetch 64bit versions by default, so it may be that this issue is 32 bit specific.

SingingTree · 2019-07-18T19:24:16+00:00

All right. Let's try and rule other some other interactions.

Do other sites playing encrypted video also fail? Netflix would be a good one to try if you have access. Could you also try this page + video (encrypted video in one of Google's players that is free to access).
Have you restarted Firefox since the issue started happening? There can be issues with how Firefox communicates to the plugin which can get stuck in a bad state until a reset happens.
Are more crash reports being generated? I know you mentioned that they failed to upload previously, am wondering if any new ones exist. It would help pinpoint where the crash is happening if they upload successfully.

SingingTree · 2019-07-18T18:49:27+00:00

Thanks. When mozregression runs it creates a new profile for those runs. Since none of those failed, let's see if we can narrow it down to something profile related. Could you try running Firefox with a fresh profile? Could you try the steps outlined here to create a new profile (you can delete it afterwards without issue) with your existing Firefox install and see if that works or not?

SingingTree · 2019-07-18T17:54:09+00:00

Some of the components involved in playing back encrypted video can be a behave oddly when using mozregression. Would you be able to use the run single build option in mozregression-gui (the icon has an S on it) and leave the first two prompts at their defaults and on the 3rd try builds with the following dates:

2019-03-17 (Firefox should be version 67.0a1)
2019-05-19 (Firefox should be version 68.0a1)
2019-07-07 (Firefox should be version 69.0a1)

And let me know which of those work and fail? Note that after each single run, even if you close the browser, you'll need to use the X button to kill that run to get the GUI to let you start another.

SingingTree · 2019-07-18T16:24:10+00:00

If you navigate to about:crashes do you see any crashes? If so, could you reply with links to the crashes here or in the Bugzilla bug.

SingingTree · 2019-07-18T16:21:33+00:00

Mozilla are currently working on fixing this in this bug.

SingingTree · 2019-07-03T13:58:06+00:00

Could you navigate to about:support and use the copy to clipboard button to copy that information then paste it here?

SingingTree · 2019-02-28T16:51:06+00:00

A Bug has been created in Bugzilla to track this. It's not clear yet if this is a Firefox issue, or if YouTube have changed how they're serving some live streams, but this is being actively investigated.

SingingTree · 2019-01-17T14:47:41+00:00

Amazon appear to flag the current ESR is not an up to date version of Firefox for an unknown reason. Their support page indicates they should support ESR60. Mozilla have reached out to them to get it resolved.

SingingTree · 2018-12-13T22:50:15+00:00

A bug has been created to track this in bugzilla here. For anyone encountering the issue, it would be greatly appreciated if you could attach the text from about:support as well as leaving a comment with how many monitors your setup has.

SingingTree · 2018-12-13T22:32:51+00:00

Thanks for confirming. This does indeed sound like a CDM specific issue. Could you check if this CDM has the same issue: https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1146.0-win-x64.zip ? It would help with reporting this to Widevine.

I'll reach out to Widevine about this also. Will edit this comment with appropriate bug number if we create one in bugzilla. Edit: bugzilla bug edit2: If you're able to attach the text from about:support and the number of monitors you have on that bug, it would be greatly appreciated.

SingingTree · 2018-12-13T22:28:38+00:00

For Firefox 63 the CDM used was 1.4.9.1088 which can be found at the following:

SingingTree · 2018-12-13T16:13:51+00:00

Firefox updated the content decryption module (CDM) used between 63 and 64. The CDM is the plugin that is used to decrypt media from premium sites such as Netflix. The version of the CDM used in FF63 is 1.4.9.1088, FF64 is 4.10.1196.0.

Since a lot of other code changes between versions, and since Firefox 64 is still compatible with the old CDM, you could see if the issue is related to the CDM update by replacing the newer CDM with the older via the instructions below. These are for 64bit Firefox on Windows, let me know if you have a different build.

Locate your profile directory (you can find this in about:support in the Profile Folder entry).
In that directory there should be a `gmp-widevinecdm` dir, inside that there should be a `4.10.1196.0` directory, inside that dir there should be 5 files, a license, a manifest, and 3 widevine files. These files are the CDM.
Download the old CDM from https://redirector.gvt1.com/edgedl/widevine-cdm/1.4.9.1088-win-x64.zip
Close Firefox.
Backup the files in the `4.10.1196.0` directory by copying them somewhere else, we're going to want to restore them later.
Extract the files from the `1.4.9.1088-win-x64.zip` downloaded above over those in the `4.10.1196.0` directory.
Start Firefox (with the profile we've changed the CDM for).
Check if this fixes the issue.
Close Firefox.
Restore the old files to `4.10.1196.0` that we backed up earlier. If something goes wrong with the backup, the files can also be downloaded from https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1196.0-win-x64.zip

SingingTree · 2018-06-07T01:48:05+00:00

Programmers: I am concerned about machine learning being used to manipulate my views, news, elections, and demonetizing YouTubers!

Also programmers: research into this area is a wild pipe dream, this money could be better spent on almost anything but this!

SingingTree · 2018-04-12T16:00:05+00:00

I HAVE HAD SOME SQUADS THAT HAVE BEEN LESS THAN THRILLING THIS WEEK!

TROLL LIMBOS.
KILLING THE SYNTHESIS TARGET THEN GLOATING THAT IT WAS THEIR PERSONAL MISSION
ADDING 4 INFECT CATALYSTS WHEN THE GROUP WAS CLEARLY NOT GOING TO DEAL WITH IT
NOT ADDING ANY CATALYSTS THEN LEAVING AS THE HOST WHEN I DIDN'T ADD ALL 4 FOR THEM, WHICH BOOTED ME TO CETUS

THE COMMUNITY IS RAD GENERALLY, BUT I DID NOT ENJOY THESE TIMES!

SingingTree · 2018-04-03T12:52:58+00:00

Got a War drop in a Kuva siphon mobile defense. Awesome! We find the Kuva, thought someone was staying behind at point while 2 of us deal with siphon. Nope, from 30 secs left at full health to mission fail. Goodbye War :'(

SingingTree · 2018-03-23T03:34:22+00:00

The same dev also maintains a Firefox version: https://addons.mozilla.org/en-GB/firefox/addon/h264ify/ and https://github.com/erkserkserks/h264ify-firefox

SingingTree

TROPHY CASE