wenduluk onilwin lavynia
Walda Caesar
Anytime I try to use Netflix, a yellow bar appears that reads "Firefox is installing components needed to play the audio or video on this page. Please try again later." I have read that checking to see that if DRM is ticked. I have unticked and re-ticked that option and still nothing works. I try and see if Widevine Content is being installed. All it says, and it always says that it "..will be installed shortly". I have looked around and some people recommend to install Widevine manually, but it is confusing and the links don't work. Please help, I want to use Firefox since I get some weird lag on videos on Chrome.
hi, firefox will attempt to automatically download the file in the background from -cdm/4.10.1440.19-win-ia32.zip - the common reason for an error here is if you have a custom hosts file that blocks access to the gvt1.com domain or if your network traffic is intercepted (by security software for example).
I am not sure how I would go about finding the right file that blocks access to the gvt1.com. I use Advanced SystemCare as my Antivirus and computer care. So, could it possibly be ASC? Also, if anyone would know how I could go about fixing it through there if that is the problem.
PROBLEM SOLVED! There was something in my hosts file that was blocking it. It was something called "redirect.gvt1 .." something like that. I deleted that then restarted computer. And everything works fine!
This is my first time here, I'm really just annoyed and would like to leave feedback somewhere. I prefer to just send an email but this seems to be the best option available.
Today I had to close my Firefox browser and open Microsoft Edge. If that isn't a huge red flag then I can't think of a better example.
I don't know what is causing it specifically, but Netflix video quality on Firefox is terrible. Simply testing on another browser and getting much better results is reason enough to me that the fault is with the firefox browser in some regard.
Microsoft Edge gave me a better experience.
Have tried re-installing Firefox esr 60.5, installing regular Firefox Quantum 65, went back to the default kernel- 4.9.126 [currently using 4.18.7], disabling extentions, enabling OpenH264 Video Codec, and updating Widevine.
As Chrome works with Netflix, that is what I currently use, but am hearing talk of Chrome soon disabling some extensions that I need and FF will not be doing that. I had stopped using Mozilla because of the crashing and other problems it had, but need to see if it is workable somehow. Thanks for the information.
_____________________________
Although it seems odd that the same banner appears with Firefox Quantum 65 installed, I think the following might be the problem, however, after installing the workaround, another site claims the old version re-installs itself:
Problem is here that the wrong version of widevine is installed for firefox-esr 60.5.0. You can manually fix this by downloading (please check the in-sources list for non-x64 binary urls [1] on in firefox using the URL chrome://global/content/gmp-sources/widevinecdm.json
It is currently unknown to me why the browser still downloads 1.4.8.1008. Even when removing my .mozilla directory. Is this inserted by some external service which still thinks that 60.x.0 is compatible to 1.4.8.1008 and not to 4.10.1196.0? I would therefore guess that the aus service of Mozilla is broken
Thanks for clarification and posting the workaround. I can see the problem now.Looking again at the debian bugreport today, I saw they posted another workaround down there by changing the app.update.channel.
Seems we have to watchup for the firefox-esr update.
Normally the upgrade of firefox-esr should overwrite the /usr/lib/firefox-esr/defaults/pref/channel-prefs.js
Maybe resetting to default shortly before doing the upgrade and looking what happens, is the best.
I wasn't able to reproduce this on Firefox 67.0.4 or Firefox 69.0a1, it is more than likely an add-on which causes the issue.
Try to disable your add-ons and then enable them one-by-one in order to find the one that causes the crash.
Can you link to any other crash reports you have sent for this? [@ IPCError-browser ShutDownKill ] is a catch all signature with many different bugs falling into it, so it would help to be able to see more of the ones specific to this bug.
Because now we're lacking of a crash report which has detailed call stack related to a real problem (no matter it's about graphic, playback or EME), it's hard for us to figure out what's going on there.
To make sure I understand the crash: Firefox crashes and the Firefox window locks up, requiring you to close Firefox and open it again (not the whole system)? When the crash happens does Firefox show any information reporting that a crash has happened before it locks? If not, does the Window just freeze in its current state, does it turn black, does something else happen?
Crashing the whole system sounds like a driver issue. Since it's happening on Netflix, I suspect changing prefs to see if this mitigates the issue may not help, as the component responsible for decoding in this scenario (the Widevine CDM) will not change behaviour based on prefs.
They seem to be unrelated and belong to bug 1566310 which has already been fixed. So that's very, very odd. I have a setup that's similar to Selim - even the same graphics driver - but no Netflix account so I can't check myself.
However if the whole machine is freezing when this happens then it might even be a hardware problem. Selim, are you experiencing instability in other programs too? What happens if you watch Netflix with another browser?
OK, if both Chrome and Firefox are affected then it's most likely be a driver issue and specifically related to the video decoding logic. Out of curiosity, what kind of graphics card do you have? Knowing the exact model I could look it up on crash-stats and see if we have more crashes for it.
I was searching for this for the past days. I recently started having this exact same issue too and I though it was firefox. It crashes sometimes when clicking play in netflix website. I also have an AMD graphics card and I updated today to the latest driver and software, but it still just happened.
My suspicion here would be that there is an issue in AMD's driver related to video decoding that causes the crash. Firefox has blacklists of drivers which it will not use for hardware decoding due to such issues, however, I would expect that Widevine has it's own blacklist which may not include these drivers -- this is consistent with the same crash happening in Chrome.
I'll reach out to Widevine regarding the issue, as they may be able to adjust their blacklists. Ideally this is something that would be fixed in the driver, but I'm not sure how to attempt to rectify that.
I tested again with Chrome for a few times but didn't succeed in reproducing the crash. Tested with Firefox after succeeding in Chrome and had an instant crash. I have no idea how often it happens with Chrome. I'll try again from time to time and update this bug if I can generate a crash report.
I'm also experiencing this in Firefox Developer Edition, though I've been unable to make Chrome crash as it works on Netflix just fine. When I go to Netflix.com as soon as the video starts to autoplay my whole system grinds to a halt and I have to do a hard reset. My Event Viewer didn't have any helpful information as far as I can tell. But for me it's just a Firefox issue.
I've got the same problem as Jason - the whole computer freezes shortly after a video/trailer starts to autoplay. There's no firefox crash report and no useful windows event log entry. When opening Netflix on Edge there's no problem.
Thanks for checking that. I missed adding a restart Firefox step in my original instructions (I'll got an amend them). If you didn't already, could you try again with a restart following the toggling?
My computer is otherwise 100% stable (video and gaming) and even Netflix used to previously work perfectly for a few years. I am not exactly sure when this behaviour changed but it has been happening for at least few months now. If I disable WidevineCDM from launcing in Firefox, Netflix does not crash until I enable it. With it enabled, it freezes my entire computer within seconds to a few minutes when viewing trailers. Sometimes when I manage to select something to watch before it freezes, I usually can finish watching the series/movie. After the freeze only a hard reboot helps. Also error logs contain no useful information.
I'm pretty sure this issue is a combination of AMD drivers for older R7 and R9 cards and WidewineCDM, but AMD drivers that previously did work does not seem to fix the issue for me so I'm leaning on a problem within WidevineCDM. It does not seem very widespread since I cannot find many threads on google about this particular problem.
I did lots of testing and I could replicate 100% of the time the crash on my Firefox. The PC would freeze and only hardresetting worked.
Funnylly I was on discord with some friends when doing that and the call was not interupted at all even 2-3 minutes after the whole screen was frozen.