Closed Bug 1646026 Opened 4 months ago Closed 3 months ago

Crash in [@ mozilla::dom::EventSourceImpl::EventSourceServiceNotifier::~EventSourceServiceNotifier]

Categories

(DevTools :: Netmonitor, defect)

defect

Tracking

(firefox-esr68 unaffected, firefox77 unaffected, firefox78 unaffected, firefox79 fixed)

RESOLVED FIXED
Firefox 79
Tracking Status
firefox-esr68 --- unaffected
firefox77 --- unaffected
firefox78 --- unaffected
firefox79 --- fixed

People

(Reporter: achronop, Assigned: smaug)

Details

Crash Data

Attachments

(1 file)

This bug is for crash report bp-b5298b14-754e-4dd4-8f83-f25900200615.

Top 10 frames of crashing thread:

0 libxul.so mozilla::dom::EventSourceImpl::EventSourceServiceNotifier::~EventSourceServiceNotifier dom/base/EventSource.cpp:313
1 libxul.so mozilla::dom::EventSourceImpl::OnStartRequest dom/base/EventSource.cpp:724
2 libxul.so nsCORSListenerProxy::OnStartRequest netwerk/protocol/http/nsCORSListenerProxy.cpp:435
3 libxul.so mozilla::net::HttpChannelChild::DoOnStartRequest netwerk/protocol/http/HttpChannelChild.cpp:700
4 libxul.so mozilla::net::HttpChannelChild::OnStartRequest netwerk/protocol/http/HttpChannelChild.cpp:547
5 libxul.so mozilla::net::ChannelEventQueue::RunOrEnqueue netwerk/ipc/ChannelEventQueue.h:264
6 libxul.so mozilla::net::HttpChannelChild::RecvOnStartRequest netwerk/protocol/http/HttpChannelChild.cpp:417
7 libxul.so mozilla::net::PHttpChannelChild::OnMessageReceived ipc/ipdl/PHttpChannelChild.cpp:636
8 libxul.so mozilla::dom::PContentChild::OnMessageReceived ipc/ipdl/PContentChild.cpp:8188
9 libxul.so mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:2166

I suck even more.

Assignee: nobody → bugs

(It is basically harmless assertion)

Pushed by opettay@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f993bff52a4e
Remove the overly strict assertion in EventSourceServiceNotifier::~EventSourceServiceNotifier,
Status: NEW → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 79
You need to log in before you can comment on or make changes to this bug.