Closed Bug 1529143 Opened 5 years ago Closed 5 years ago

Random tab crashes with Pipe Error/Warning

Categories

(Firefox :: Untriaged, defect)

Product:
Firefox
Component:
Untriaged
Version:
65 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1521370

People

(Reporter: steven, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0

Steps to reproduce:

I was attempting to browse the internet like normal to volunteermatch.org after installing the Windows 10 1809 update.

Actual results:

On Firefox 65 after installing the Windows 1809 update, it has began crashing on random websites. The two sites that I know it crashes on are volunteermatch.org and support.mozilla.org. The -console flag gives the following error for both sites:

[Parent 16596, Gecko_IOThread] WARNING: file z:/build/build/src/ipc/chromium/src/base/process_util_win.cc, line 166

I also get errors when opening new tabs:

[Parent 16596, Gecko_IOThread] WARNING: pipe error: 109: file z:/build/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 332
[Parent 16596, Gecko_IOThread] WARNING: pipe error: 232: file z:/build/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 493

I do have full ASLR enabled via Windows Defender Exploit Protection (Force randomization for images - mandatory ASLR) as a security best practice. It is possible that this could be causing the issues given Microsoft's track record when it comes to these things.

Expected results:

I should have been able to view the volunteermatch.org website.

Please provide a crash id from about:crashes

Flags: needinfo?(steven)

Here's the id from the most recent crash:

bp-a3191dac-2d73-4af2-9b9d-a8ee00190220

Upon viewing the report myself, it may have to do with the Windows Media Feature Pack. The DLL being referenced is a part of that pack. I am running an N version of Windows 10, so I did have to manually install it.

Flags: needinfo?(steven)

Thank you very much for the crash report.
This is caused by a bug in the Windows VP9 video codec and the crash seems to happen only in the Windows N version.

There is a workaround available with changing media.wmf.vp9.enabled to false in about:config

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.