Closed Bug 1628262 Opened 5 years ago Closed 4 years ago

Crash in [@ mozilla::net::HttpChannelChild::~HttpChannelChild]

Categories

(Core :: Networking: HTTP, defect, P2)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1627946
Tracking Status
firefox-esr68 --- unaffected
firefox75 --- unaffected
firefox76 --- unaffected
firefox77 --- wontfix
firefox78 --- wontfix

People

(Reporter: sg, Unassigned)

References

(Regression)

Details

(Keywords: crash, regression, Whiteboard: [necko-triaged])

Crash Data

Attachments

(1 file)

This bug is for crash report bp-d83ea93b-1ecf-4343-a726-e2e780200408.

Top 10 frames of crashing thread:

0 xul.dll mozilla::net::HttpChannelChild::~HttpChannelChild netwerk/protocol/http/HttpChannelChild.cpp:210
1 xul.dll mozilla::net::HttpChannelChild::~HttpChannelChild netwerk/protocol/http/HttpChannelChild.cpp:204
2 xul.dll mozilla::net::HttpChannelChild::Release netwerk/protocol/http/HttpChannelChild.cpp:276
3 xul.dll mozilla::detail::RunnableMethodImpl< xpcom/threads/nsThreadUtils.h:1220
4 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1220
5 xul.dll NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:481
6 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:87
7 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:308
8 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:290
9 xul.dll nsBaseAppShell::Run widget/nsBaseAppShell.cpp:137

A diagnostic assertion is hit here, for this report with the reason ~HttpChannelChild 0000015C40B84000, mOnStopRequestCalled=false, mStatus=0x804b0002, mActorDestroyReason=1, mRedirectChannelChild=0000000000000000.

This started with build id 20200407093520, so far a few reports from Windows and Mac, none from Linux.

Priority: -- → P2
Whiteboard: [necko-triaged]
Regressed by: 1605895
Has Regression Range: --- → yes

I've had this while spamming command+shift+r on web.whatsapp.com, that was behaving weirdly (js error in their code: window.Exe is not defined), on latest Nightly on macOS.

https://crash-stats.mozilla.org/report/index/6760e975-0e47-41ee-b5c8-c689b0200409

The volume is significant on beta, Nhi could you help us get this bug triaged and assigned to somebody? Thanks

Flags: needinfo?(nhnguyen)

Junior, could you take a look? Thanks!

Flags: needinfo?(nhnguyen) → needinfo?(juhsu)

People, this is the diagnostic assertion I've added. It's early-beta only and has the same rate as the original bug we are trying to investigate. There is an updated version of the patch to provide more information in the original bug, waiting for review.

Michal, can you please look again at that review? I am sorry I reacted to that so long the first time, your request for update got lost in my emails. Thanks.

Flags: needinfo?(michal.novotny)

I accepted that patch yesterday (sorry for the delay). Is there anything else I should do now?

Flags: needinfo?(michal.novotny)

(In reply to Michal Novotny [:michal] from comment #6)

I accepted that patch yesterday (sorry for the delay). Is there anything else I should do now?

Hmm.. I again missed that email... There is nothing else for you to do. Thanks!

Flags: needinfo?(juhsu)

In bug 1596295, We caught a case that there is non-empty channel event queue when HttpChannelChild's destructor.
That might be related.

I can reproduce this crash consistently on https://www.lg.com/us/mobile-phones/v40-thinq/specs

bp-aec3a5b3-5014-4943-bfef-3d32d0200529
bp-8f851f00-1822-4554-9425-8ce720200529
bp-37cbfc2f-60b4-4db5-90f1-bce730200529

Adding about:support in the next comment.

Disabling the "LocalCDN (fork from Decentraleyes)" extension works around the issue in my profile.

(In reply to Asif Youssuff from comment #9)

I can reproduce this crash consistently on https://www.lg.com/us/mobile-phones/v40-thinq/specs

bp-aec3a5b3-5014-4943-bfef-3d32d0200529
bp-8f851f00-1822-4554-9425-8ce720200529
bp-37cbfc2f-60b4-4db5-90f1-bce730200529

Adding about:support in the next comment.

Disabling the "LocalCDN (fork from Decentraleyes)" extension works around the issue in my profile.

Thanks. The status code of the channel in your reports is different than the one I often see in public crash reports (NS_OK vs NS_ERROR_ABORT). According how many (many!) addons you have installed, I suspect this to be addon related. I can try to install some of them and try to reproduce, tho.

(In reply to Asif Youssuff from comment #9)

I can reproduce this crash consistently on https://www.lg.com/us/mobile-phones/v40-thinq/specs

bp-aec3a5b3-5014-4943-bfef-3d32d0200529
bp-8f851f00-1822-4554-9425-8ce720200529
bp-37cbfc2f-60b4-4db5-90f1-bce730200529

Adding about:support in the next comment.

Disabling the "LocalCDN (fork from Decentraleyes)" extension works around the issue in my profile.

I can reproduce with the extensions installed. But it's not possible to diagnose this (crashes with logging on - bug 1642318) and doesn't fail when attached to a debugger... back to square 1.

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

Attachment

General

Creator:
Created:
Updated:
Size: