Closed
Bug 1274279
Opened 9 years ago
Closed 9 years ago
Crash in nsStreamListenerWrapper::OnStopRequest
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox48 | --- | unaffected |
firefox49 | + | fixed |
People
(Reporter: nayinain, Assigned: jduell.mcbugs)
References
(Regression)
Details
(Keywords: crash, regression, reproducible, Whiteboard: [necko-active])
Crash Data
Attachments
(1 file)
141.90 KB,
image/png
|
Details |
This bug was filed from the Socorro interface and is
report bp-8a84a6a8-542d-489e-89c1-97a3e2160519.
=============================================================
Comment 1•9 years ago
|
||
There are 4 reports from today with this crash. They all look from the same profile.
The stack is going through js between the nsIChannel and the nsStreamListenerWrapper. Does this suggest an extension or addon? I see a lot of stuff installed in these reports:
{7067a92c-1db4-4e5e-869c-25f841287f8b} 0.2.4.2
{F632A5EA-F825-4AE7-94B5-233CFBA9F423} 0.3.7.9.18.1
ead@ziyunfei 2.0
userChromeJS@mozdev.org 2.0
autoproxy_fix@autoproxy.org 0.4b2.2013051811.5
{d166ee2a-36bb-4f33-aff7-e85f912df509} 1.2.0
{46551EC9-40F0-4e47-8E18-8E5CF550CFB8} 1.4.3
support@lastpass.com 3.3.1
omnibar@ajitk.com 0.7.28.20141004.1
inspector@mozilla.org 2.0.16.1-signed
{54BB9F3F-07E5-486c-9B39-C7398B99391C} 5.0.2015060501
{e4a8a97b-f2ed-450b-b12d-ee082ba24781} 2016.04.19.nightly
{37fa1426-b82d-11db-8314-0800200c9a66} 3.5.20
firegestures@xuldev.org 1.10.9
{c0c588b6-b11d-4898-af00-079fed05aa32} 50
privateTab@infocatcher 0.1.9.1
fbt@quicksaver 2.1.9
{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d} 2.7.3.4172-beta
e10srollout@mozilla.org 1.0
webcompat@mozilla.org 1.0
loop@mozilla.org 1.3.2
firefox@getpocket.com 1.0.3b1
reporter, are you able to reproduce the crash?
If yes, could you test in safe mode and with a fresh profile, please.
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
Flags: needinfo?(nayinain)
Keywords: crash
Steps to reproduce:
1. Install the "Mason" extension (https://addons.mozilla.org/en-US/firefox/addon/mason/?src=search).
2. As shown in the figure to add a "redirect request" rule.
3. Open "https://bugzilla.mozilla.org/show_bug.cgi?id=1274279"
results: Crash (https://crash-stats.mozilla.com/report/index/cfd5a0be-d517-4698-bbdd-6a1da2160520)
Work well in Nightly 2016-05-17 (https://hg.mozilla.org/mozilla-central/rev/a884b96685aa13b65601feddb24e5f85ba861561)
Sorry for my bad English.
Thanks for the STR.
Reg range:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=c9b617e7a39f1cd6e7a200cbb3b034c0530b19db&tochange=0d5cc353d9e014cba6dcc90cff10b7c2c17df5ea
Jason, can you check why your patch crashes Firefox in this scenario?
Blocks: 759819
Status: UNCONFIRMED → NEW
Has Regression Range: --- → yes
Has STR: --- → yes
status-firefox48:
--- → unaffected
status-firefox49:
--- → affected
tracking-firefox49:
--- → ?
Ever confirmed: true
Flags: needinfo?(jduell.mcbugs)
Keywords: regression,
reproducible
Version: unspecified → 49 Branch
Updated•9 years ago
|
Assignee: nobody → jduell.mcbugs
Whiteboard: [necko-active]
Updated•9 years ago
|
Crash Signature: [@ nsStreamListenerWrapper::OnStopRequest] → [@ nsStreamListenerWrapper::OnStopRequest] [@ mozilla::net::nsStreamListenerWrapper::OnStopRequest]
Assignee | ||
Comment 7•9 years ago
|
||
I've backed out the offending patch, which should fix the crashes.
https://hg.mozilla.org/integration/mozilla-inbound/rev/7f39530aedec
Flags: needinfo?(jduell.mcbugs)
Comment 8•9 years ago
|
||
Did this ever land on m-c? Usually when stuff gets merged, that shows up in the bug.
Flags: needinfo?(jduell.mcbugs)
Comment 9•9 years ago
|
||
These crash signatures aren't showing up now, so it seems likely that the backout did land.
Updated•9 years ago
|
Comment 11•9 years ago
|
||
Crash signatures no longer showing up in 49, marking this fixed.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•1 year ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•