Since upgrading windows N with the windows media pack, Firefox immediately crashes on opening various different websites - mostly video ones (Netflix, any youtube.com/watch...) but also mozilla support. Prior to installing the media pack, youtube videos would play but Netflix would not (but no crashes).
Problem persists in safe mode, with DRM content allowed and not, and with hardware acceleration disabled. Flaser player and video drivers are installed and up to date; Microsoft Silverlight is also installed.
Most recent crash report IDs are:
bp-0a7d8acd-1afe-4eba-bb2d-5dfaf0190224 24/02/2019, 10:14 bp-bf9351db-1243-4ea8-bfcb-8ec560190224 24/02/2019, 10:14 bp-fef6d1c3-cd7e-4935-820e-bda130190224 24/02/2019, 10:14 bp-e52d8e6f-4c27-4ccb-af94-cf4000190224 24/02/2019, 10:14 bp-dd8c5c8f-f180-4afb-80f9-44ac90190224 24/02/2019, 10:14 bp-8eca40c2-3e2d-448f-8ead-36a990190224 24/02/2019, 10:14 bp-459e11ce-d3cb-4d85-807f-804910190224 24/02/2019, 10:14 bp-8551690f-9593-4d56-ba6f-ff5770190224 24/02/2019, 10:14 bp-0f7d679c-c0de-433d-bd7f-dd8ca0190224 24/02/2019, 10:14
hi, this should be a workaround to avoid the tab crashes: enter about:config into the firefox address bar (confirm the info message in case it shows up) & search for the preference named media.wmf.vp9.enabled. double-click it and change its value to false, then restart firefox once.從原來的回覆中察看解決方案 1
- User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; .NET4.0C; .NET4.0E; .NET CLR 2.0.50727; .NET CLR 3.0.30729; .NET CLR 3.5.30729; Zoom 3.6.0; rv:11.0) like Gecko
- Flash player, obviously
prior to media pack, gifs/videos would not play on twitter, imgur etc. but now do work fine (and not cause crashes)
we're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.
The crash report is several pages of data. We need the report numbers to see the whole report.
- Enter about:crashes in the Firefox address bar and press Enter. A list of Submitted/Unsubmitted Crash Reports will appear, similar to the one shown below.
- Copy the 5 most recent Submitted Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.
Note: If a recent Report ID does not start with bp- click on it to submit the report.
(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)
Thank you for your help!
More information and further troubleshooting steps can be found in the Firefox crashes - Troubleshoot, prevent and get help fixing crashes article.
Best regards, David-Walczysko Volunteer supporter
Are the ones linked in the original post not sufficient? Here's a few more, anyway
bp-f7855168-c7c5-41ff-8917-7c8f70190224 bp-9e0b0730-be03-4acd-a467-cc08a0190224 bp-f87c6925-17b5-4c76-b112-ed52e0190224 bp-0a7d8acd-1afe-4eba-bb2d-5dfaf0190224 bp-bf9351db-1243-4ea8-bfcb-8ec560190224
Product Firefox Release Channel release Version 65.0.1 Build ID 20190211233335 (2019-02-11) OS Windows 10 OS Version 10.0.17763
bp-f7855168-c7c5-41ff-8917-7c8f70190224 bp-9e0b0730-be03-4acd-a467-cc08a0190224 bp-f87c6925-17b5-4c76-b112-ed52e0190224
Uptime 16 seconds
Crash Reason EXCEPTION_ACCESS_VIOLATION_WRITE
MSVP9DEC.dll = Microsoft Corporation
This is for Sumo's Related Bugs 1521370 NEW --- Reproducible tab crashes after update to Windows 10 1809
Mozilla is in contact with Microsoft on this issue.
hi, this should be a workaround to avoid the tab crashes: enter about:config into the firefox address bar (confirm the info message in case it shows up) & search for the preference named media.wmf.vp9.enabled. double-click it and change its value to false, then restart firefox once.
That worked perfectly, thanks! When you say it's a workaround, do you mean it shouldn't be used as a permanent solution?
Either way, thanks for the help! Nick
according to the info we got from microsoft this may be fixed through the next major spring feature update (1903?) - you could try to toggle back the preference to its default value afterwards...
the preference shouldn't make to much of a difference anyway during normal browsing anyway, so you could also treat it as a permanent "workaround" too :))