crash in mozilla::net::OnTransportStatusAsyncEvent::Run @ mozilla::net::nsHttpChannel::OnTransportStatus

RESOLVED WORKSFORME

Status

()

Core
Networking: HTTP
--
critical
RESOLVED WORKSFORME
5 years ago
2 years ago

People

(Reporter: Scoobidiver (away), Assigned: sworkman)

Tracking

({crash, regression})

24 Branch
x86
Windows 7
crash, regression
Points:
---

Firefox Tracking Flags

(firefox23 unaffected, firefox24 fixed)

Details

(crash signature)

(Reporter)

Description

5 years ago
It first showed up in 24.0a1/201306015. The regression range is:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b197bed90a98&tochange=3d16d59c9317
It's likely a regression from bug 497003.

Signature 	mozilla::net::nsHttpChannel::OnTransportStatus(nsITransport*, tag_nsresult, unsigned __int64, unsigned __int64) More Reports Search
UUID	0c43c3b2-ded9-4789-bc3e-e15662130617
Date Processed	2013-06-17 04:16:56
Uptime	43
Last Crash	59.7 minutes before submission
Install Age	1.1 hours since version was first installed.
Install Time	2013-06-17 03:10:19
Product	Firefox
Version	24.0a1
Build ID	20130616031139
Release Channel	nightly
OS	Windows NT
OS Version	6.1.7601 Service Pack 1
Build Architecture	x86
Build Architecture Info	GenuineIntel family 6 model 15 stepping 6
Crash Reason	EXCEPTION_ACCESS_VIOLATION_READ
Crash Address	0x0
User Comments	Searching in wiki, crashed when pressed ENTER
App Notes 	
AdapterVendorID: 0x10de, AdapterDeviceID: 0x0611, AdapterSubsysID: 053c10de, AdapterDriverVersion: 9.18.13.697
D2D? D2D+ DWrite? DWrite+ D3D10 Layers? D3D10 Layers+ 
Processor Notes 	sp-processor03_phx1_mozilla_com_27827:2012
EMCheckCompatibility	True
Adapter Vendor ID	0x10de
Adapter Device ID	0x0611
Total Virtual Memory	4294836224
Available Virtual Memory	3676098560
System Memory Use Percentage	31
Available Page File	14046130176
Available Physical Memory	5857505280

Frame 	Module 	Signature 	Source
0 	xul.dll 	mozilla::net::nsHttpChannel::OnTransportStatus 	netwerk/protocol/http/nsHttpChannel.cpp:5333
1 	xul.dll 	mozilla::net::OnTransportStatusAsyncEvent::Run 	netwerk/protocol/http/nsHttpChannel.cpp:5152
2 	xul.dll 	nsThread::ProcessNextEvent 	xpcom/threads/nsThread.cpp:626
3 	xul.dll 	NS_ProcessNextEvent 	obj-firefox/xpcom/build/nsThreadUtils.cpp:238
4 	xul.dll 	mozilla::ipc::MessagePump::Run 	ipc/glue/MessagePump.cpp:82
5 	xul.dll 	MessageLoop::RunHandler 	ipc/chromium/src/base/message_loop.cc:212
6 	xul.dll 	MessageLoop::Run 	ipc/chromium/src/base/message_loop.cc:186
7 	xul.dll 	nsBaseAppShell::Run 	widget/xpwidgets/nsBaseAppShell.cpp:163
8 	xul.dll 	nsAppShell::Run 	widget/windows/nsAppShell.cpp:113
9 	xul.dll 	nsAppStartup::Run 	toolkit/components/startup/nsAppStartup.cpp:269
10 	xul.dll 	XREMain::XRE_mainRun 	toolkit/xre/nsAppRunner.cpp:3856
11 	xul.dll 	XREMain::XRE_main 	toolkit/xre/nsAppRunner.cpp:3924
12 	xul.dll 	XRE_main 	toolkit/xre/nsAppRunner.cpp:4137
13 	firefox.exe 	do_main 	browser/app/nsBrowserApp.cpp:272
14 	firefox.exe 	NS_internal_main 	browser/app/nsBrowserApp.cpp:632
15 	firefox.exe 	wmain 	toolkit/xre/nsWindowsWMain.cpp:105
16 	firefox.exe 	__tmainCRTStartup 	crtexe.c:552
17 	kernel32.dll 	BaseThreadInitThunk 	
18 	ntdll.dll 	__RtlUserThreadStart 	
19 	ntdll.dll 	_RtlUserThreadStart 	

More reports at:
https://crash-stats.mozilla.com/report/list?signature=mozilla%3A%3Anet%3A%3AnsHttpChannel%3A%3AOnTransportStatus%28nsITransport*%2C+tag_nsresult%2C+unsigned+__int64%2C+unsigned+__int64%29
(Assignee)

Comment 1

5 years ago
Crash should have been fixed by backout of patches pertaining to Bug 497003, but I'm still working on identifying why the crash happened.
Assignee: nobody → sworkman
Status: NEW → ASSIGNED
(Reporter)

Updated

5 years ago
status-firefox24: affected → fixed

Updated

3 years ago
Crash Signature: [@ mozilla::net::nsHttpChannel::OnTransportStatus(nsITransport*, tag_nsresult, unsigned __int64, unsigned __int64)] → [@ mozilla::net::nsHttpChannel::OnTransportStatus(nsITransport*, tag_nsresult, unsigned __int64, unsigned __int64)] [@ mozilla::net::nsHttpChannel::OnTransportStatus]
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.