724389 - [adbe 3142336] Flash plugin hang in F1143089219

Status: RESOLVED INCOMPLETE

(External Software Affecting Firefox Graveyard :: Flash (Adobe), defect)

Description

[Scoobidiver (away)]

It's #1 top plugin hanger in 10.0, but many crash reports are browser hangs (see bug 560549).

Signature 	hang | NtUserPeekMessage More Reports Search
UUID	3e68c281-51f6-4c72-a837-f84d12120204
Date Processed	2012-02-04 21:05:56
Process Type	plugin Version: Filename: NPSWF32.dll
Uptime	15600
Install Age	1.4 days since version was first installed.
Install Time	2012-02-03 07:36:50
Product	Firefox
Version	10.0
Build ID	20120129021758
Release Channel	release
OS	Windows NT
OS Version	6.1.7601 Service Pack 1
Build Architecture	x86
Build Architecture Info	GenuineIntel family 6 model 23 stepping 10
Crash Reason	EXCEPTION_BREAKPOINT
Crash Address	0x762a0735
App Notes 	
AdapterVendorID: 10de, AdapterDeviceID: 086e, AdapterSubsysID: 76211462, AdapterDriverVersion: 8.17.11.9562
D3D10 Layers? D3D10 Layers-
D3D9 Layers? D3D9 Layers-
EMCheckCompatibility	True

Frame 	Module 	Signature [Expand] 	Source
0 	user32.dll 	NtUserPeekMessage 	
1 	user32.dll 	NtUserPeekMessage 	
2 	user32.dll 	_PeekMessage 	
3 	user32.dll 	NtUserPeekMessage 	
4 	NPSWF32.dll 	F1143089219________________________________ 	F806924378_____________________________________________________________________:3406
5 	NPSWF32.dll 	F1546913566_____________________________________ 	F806924378_____________________________________________________________________:3783
6 	NPSWF32.dll 	F957328252________________________ 	F806924378_____________________________________________________________________:620
7 	user32.dll 	InternalCallWinProc 	
8 	user32.dll 	UserCallWinProcCheckWow 	
9 	user32.dll 	CallWindowProcAorW 	
10 	user32.dll 	CallWindowProcW 	
11 	xul.dll 	mozilla::plugins::PluginInstanceChild::FlashThrottleAsyncMsg::Run 	dom/plugins/ipc/PluginInstanceChild.cpp:2024
12 	xul.dll 	MessageLoop::RunTask 	ipc/chromium/src/base/message_loop.cc:318
13 	xul.dll 	MessageLoop::DeferOrRunPendingTask 	ipc/chromium/src/base/message_loop.cc:326
14 	xul.dll 	MessageLoop::DoDelayedWork 	
15 	xul.dll 	base::MessagePumpForUI::DoRunLoop 	ipc/chromium/src/base/message_pump_win.cc:219
16 	xul.dll 	base::MessagePumpWin::RunWithDispatcher 	ipc/chromium/src/base/message_pump_win.cc:53
17 	xul.dll 	base::MessagePumpWin::Run 	ipc/chromium/src/base/message_pump_win.h:78
18 	xul.dll 	MessageLoop::RunInternal 	ipc/chromium/src/base/message_loop.cc:208
19 	xul.dll 	MessageLoop::RunHandler 	
20 	xul.dll 	MessageLoop::Run 	ipc/chromium/src/base/message_loop.cc:175
21 	xul.dll 	XRE_InitChildProcess 	toolkit/xre/nsEmbedFunctions.cpp:524
22 	plugin-container.exe 	wmain 	toolkit/xre/nsWindowsWMain.cpp:107
23 	plugin-container.exe 	__tmainCRTStartup 	crtexe.c:594
24 	kernel32.dll 	BaseThreadInitThunk 	
25 	ntdll.dll 	__RtlUserThreadStart 	
26 	ntdll.dll 	_RtlUserThreadStart 	

NPSWF32.dll 	11.1.102.55 	AEBCF68A3E74455994C9CCE79744EF541 	NPSWF32.pdb

More reports at:
https://crash-stats.mozilla.com/report/list?signature=hang%20|%20NtUserPeekMessage

Comment 1

[smadayag]

would it be possible to point out a report with FP 11,1,102,63?  there were similar reports in Microsoft's WER for 11,1,102,62, but it is no longer reported in the latest player.  i'm hopeful the issue is resolved...

Comment 2

[Scoobidiver (away)]

Take a look at the signature summary:
11.1.102.62 	30.666 % 	3985
11.1.102.55 	22.024 % 	2862
11.1.102.63 	16.491 % 	2143

Comment 3

[smadayag]

thanks Scoobidiver.  i neglected to look at the summary...

Comment 4

[smadayag]

dev is asking for a few things that may help see where the issue can be.

crash dumps for the browser side.
STR
info about the message that is being handled by Peekmessage at the time of the hang

the above would assist in troubleshooting now.

he also states, 
...in our Cyril release with protected mode, we have specific mechanisms for avoiding hangs due to window messages that involve multiple threads.

If we can't get any of the requested info (crash dumps, a repro case, info about the message handled by PeekMessage) then perhaps we can just wait until Cyril ships and see if this hang decreases.

Comment 5

[Scoobidiver (away)]

(In reply to smadayag from comment #4)
> crash dumps for the browser side.
bp-4f5bcd91-01de-4352-b407-e115e2120323

Comment 6

[smadayag]

(In reply to Scoobidiver from comment #5)
> (In reply to smadayag from comment #4)
> > crash dumps for the browser side.
> bp-4f5bcd91-01de-4352-b407-e115e2120323

matt pointed out that flash isn't loaded in that example.  would you have another?

Comment 7

[Scoobidiver (away)]

It s(In reply to smadayag from comment #6)
> would you have another?
Flash is only loaded in the plugin hang, not in the browser hang.

Removing the topcrash keyword as the crash signature with this stack is not a high volume hanger. But bug 726425 is a top hanger.

Comment 8

[Benjamin Smedberg]

I'm closing a lot of bugs which are filed as Adobe Flash bugs which are either irrelevant, not actionable, or not serious enough to track in the Mozilla bug tracker. For the most part, Flash bugs should be filed in Adobe bugbase, and we'll only track a few highly-critical issues in the Mozilla tracker.

Comment 9

[BMO Automation]

Version and milestone values are being reset to defaults as part of product refactoring.