Closed Bug 1638377 Opened 5 years ago Closed 5 years ago

Crash in [@ mozilla::dom::(anonymous namespace)::ScriptResponseHeaderProcessor::OnStopRequest]

Categories

(Core :: DOM: Workers, defect, P5)

defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox76 --- unaffected
firefox77 --- wontfix
firefox78 --- wontfix

People

(Reporter: mccr8, Unassigned)

References

(Regression)

Details

(Keywords: crash, regression)

Crash Data

This bug is for crash report bp-d1b2bf3b-f180-43f8-86ae-deb0a0200514.

Top 10 frames of crashing thread:

0 libxul.so mozilla::dom:: dom/workers/ScriptLoader.cpp:595
1 libxul.so mozilla::net::nsStreamLoader::OnStopRequest netwerk/base/nsStreamLoader.cpp:102
2 libxul.so mozilla::extensions::StreamFilterParent::EmitStopRequest toolkit/components/extensions/webrequest/StreamFilterParent.cpp:580
3 libxul.so mozilla::net::ChannelEventQueue::FlushQueue netwerk/ipc/ChannelEventQueue.cpp:90
4 libxul.so mozilla::net::ChannelEventQueue::ResumeInternal netwerk/ipc/ChannelEventQueue.cpp:148
5 libxul.so nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1211
6 libxul.so mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:109
7 libxul.so MessageLoop::Run ipc/chromium/src/base/message_loop.cc:290
8 libxul.so nsBaseAppShell::Run widget/nsBaseAppShell.cpp:137
9 libxul.so XRE_RunAppShell toolkit/xre/nsEmbedFunctions.cpp:909

There are only 5 crashes with this signature, from 2 installations, but it is a diagnostic assert in recent code so I figured I'd file this.

The crash reason is: MOZ_DIAGNOSTIC_ASSERT(mWorkerPrivate->GetEmbedderPolicy().isSome())
The actual code we're crashing on is:
MOZ_DIAGNOSTIC_ASSERT_IF(NS_SUCCEEDED(aStatusCode), mWorkerPrivate->GetEmbedderPolicy().isSome());

It looks like this was added in bug 1575090.

Set release status flags based on info from the regressing bug 1575090

Severity: -- → S4
Priority: -- → P5

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.