Scoobidiver (away) Reporter
	Description • 13 years ago

They are crash signatures that spiked in 13.0a1/20120223.
The regression range for the spike is:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=373c710112e6&tochange=5e756e59a794

Signature 	DispatchHookA More Reports Search
UUID	803b0529-b722-4fb5-862f-05ce22120223
Date Processed	2012-02-23 17:49:54
Uptime	10
Last Crash	15 seconds before submission
Install Age	53 seconds since version was first installed.
Install Time	2012-02-23 17:48:54
Product	Firefox
Version	13.0a1
Build ID	20120223031236
Release Channel	nightly
OS	Windows NT
OS Version	6.1.7601 Service Pack 1
Build Architecture	amd64
Build Architecture Info	family 6 model 42 stepping 7
Crash Reason	EXCEPTION_ACCESS_VIOLATION_EXEC
Crash Address	0x100439a0
App Notes 	
AdapterVendorID: 0x1002, AdapterDeviceID: 0x6741, AdapterSubsysID: 00e3106b, AdapterDriverVersion: 8.850.0.0
Processor Notes 	WARNING: JSON file missing Add-ons
EMCheckCompatibility	True	
Total Virtual Memory	8796092891136
Available Virtual Memory	8795865186304
System Memory Use Percentage	25
Available Page File	14189449216
Available Physical Memory	6327640064

Frame 	Module 	Signature [Expand] 	Source
0 		@0x100439a0 	
1 	user32.dll 	DispatchHookA 	
2 	user32.dll 	UserCallWinProcCheckWow 	
3 	user32.dll 	UserCallWinProcCheckWow 	
4 	user32.dll 	fnHkINLPCWPSTRUCTA 	
5 	user32.dll 	_fnDWORD 	
6 	user32.dll 	UserCallWinProcCheckWow 	
7 	user32.dll 	PeekMessageW 	
8 	ntdll.dll 	KiUserCallbackDispatcher 	
9 	user32.dll 	ZwUserDispatchMessage 	
10 	xul.dll 	PeekUIMessage 	widget/windows/nsAppShell.cpp:89
11 	ntdll.dll 	NtdllGhostWndProc_W 	
12 	user32.dll 	ZwUserDispatchMessage 	
13 	user32.dll 	PeekMessageW 	
14 	user32.dll 	TranslateMessage 	
15 	xul.dll 	nsIFrame::AddCSSFlex 	layout/xul/base/src/nsBox.cpp:915
16 	xul.dll 	nsAppShell::ProcessNextNativeEvent 	widget/windows/nsAppShell.cpp:344
17 	xul.dll 	xul.dll@0x1944bf 	
18 	xul.dll 	nsBaseAppShell::OnProcessNextEvent 	widget/xpwidgets/nsBaseAppShell.cpp:324
19 	xul.dll 	nsThread::ProcessNextEvent 	xpcom/threads/nsThread.cpp:619
20 	xul.dll 	nsDOMEvent::GetEventPopupControlState 	content/events/src/nsDOMEvent.cpp:1013
21 	xul.dll 	JS_SuspendRequest 	js/src/jsapi.cpp:1084
22 	nspr4.dll 	PR_GetCurrentThread 	nsprpub/pr/src/threads/prcthr.c:174
23 	xul.dll 	NS_ProcessNextEvent_P 	obj-firefox/xpcom/build/nsThreadUtils.cpp:245
24 	xul.dll 	nsXULWindow::ShowModal 	xpfe/appshell/src/nsXULWindow.cpp:420
25 	xul.dll 	nsContentTreeOwner::ShowAsModal 	xpfe/appshell/src/nsContentTreeOwner.cpp:564
26 	xul.dll 	nsWindowWatcher::OpenWindowJSInternal 	

More reports at:
https://crash-stats.mozilla.com/report/list?signature=DispatchHookA
https://crash-stats.mozilla.com/report/list?signature=fnHkINLPCWPSTRUCTA

	David Baron :dbaron:
	Comment 1 • 13 years ago

This stack is garbled (enough that I don't believe any of it) and does not implicate Layout code.

	David Baron :dbaron:
	Comment 2 • 13 years ago

I shouldn't quite say that.  These parts are believable:

13 	user32.dll 	PeekMessageW 	
14 	user32.dll 	TranslateMessage 	
16 	xul.dll 	nsAppShell::ProcessNextNativeEvent 	widget/windows/nsAppShell.cpp:344
18 	xul.dll 	nsBaseAppShell::OnProcessNextEvent 	widget/xpwidgets/nsBaseAppShell.cpp:324
19 	xul.dll 	nsThread::ProcessNextEvent 	xpcom/threads/nsThread.cpp:619
23 	xul.dll 	NS_ProcessNextEvent_P 	obj-firefox/xpcom/build/nsThreadUtils.cpp:245
24 	xul.dll 	nsXULWindow::ShowModal 	xpfe/appshell/src/nsXULWindow.cpp:420
25 	xul.dll 	nsContentTreeOwner::ShowAsModal 	xpfe/appshell/src/nsContentTreeOwner.cpp:564
26 	xul.dll 	nsWindowWatcher::OpenWindowJSInternal

	Kyle Huey (Exited; not receiving bugmail, old account, do not use)
	Comment 3 • 13 years ago

I think this will be fixed by Bug 730051.

	Scoobidiver (away) Reporter
	Comment 4 • 13 years ago

(In reply to Kyle Huey [:khuey] (khuey@mozilla.com) from comment #3)
> I think this will be fixed by Bug 730051.
The latest DispatchHookA crash happened in 13.0a1/20120301 so it's indeed true.
The latest fnHkINLPCWPSTRUCTA crash happened in 13.0a1/2012022416 so it has been fixed by another bug.