561467 - Crash with Adobe Reader 8 or 9 @ UserCallWinProcCheckWow

Status: RESOLVED INCOMPLETE

(Plugins Graveyard :: PDF (Adobe), defect)

Description

[u348128]

bp-bfe0e1a3-a235-4b57-8189-121802100423

Go to:

http://people.cohums.ohio-state.edu/tennant9/

On the left menu, click articles.

Click on:

'Perfect validity, entailment and paraconsistency',

(near 86, can change).

Click 'Free Preview'.

Click back button.

BOOM!!!

100% crash.

My Acrobat reader is: 8.1.3.187.
Is not the newest one. Maybe already solved in newer version.

Lucas

Comment 1

[timeless]

Signature	nanojit::ExprFilter::insGuard(nanojit::LOpcode, nanojit::LIns*, nanojit::GuardRecord*)
UUID	bfe0e1a3-a235-4b57-8189-121802100423
Time 	2010-04-23 14:24:25.804029
Uptime	76
Last Crash	79 seconds before submission
Product	Firefox
Version	3.6.3
Build ID	20100401080539
Branch	1.9.2
OS	Windows NT
OS Version	5.1.2600 Service Pack 3
CPU	x86
CPU Info	GenuineIntel family 15 model 2 stepping 9
Crash Reason	EXCEPTION_ACCESS_VIOLATION
Crash Address	0x32003d
User Comments	
Processor Notes 	
Crashing Thread
Frame 	Module 	Signature [Expand] 	Source
0 	js3250.dll 	nanojit::ExprFilter::insGuard 	
1 	user32.dll 	UserCallWinProcCheckWow 	
2 	user32.dll 	CallWindowProcAorW 	
3 	user32.dll 	CallWindowProcA 	
4 	nppdf32.dll 	nppdf32.dll@0x67af 	
5 	user32.dll 	InternalCallWinProc 	
6 	user32.dll 	UserCallWinProcCheckWow 	
7 	user32.dll 	DispatchClientMessage 	
8 	user32.dll 	__fnDWORD 	
9 	ntdll.dll 	KiUserCallbackDispatcher 	
10 	nppdf32.dll 	nppdf32.dll@0x66a5 	
11 	user32.dll 	DispatchMessageW 	
12 	xul.dll 	nsAppShell::ProcessNextNativeEvent 	widget/src/windows/nsAppShell.cpp:179

nppdf32.dll 	8.1.3.187 	712930D94EE2489EBD2E4B40CE845AAB1 	Nppdf32.pdb

Comment 2

[Nicholas Nethercote [inactive]]

(In reply to comment #1)
> Frame     Module     Signature [Expand]     Source
> 0     js3250.dll     nanojit::ExprFilter::insGuard     
> 1     user32.dll     UserCallWinProcCheckWow     
> 2     user32.dll     CallWindowProcAorW     
> 3     user32.dll     CallWindowProcA     

That's odd.  Normally a call to nanojit::ExprFilter::insGuard would be preceded by several more stack entries within nanojit.  That makes me think there's a bogus jump that just happens to land in insGuard.

Comment 3

[Scoobidiver (away)]

Here is a recent stack trace:
Frame 	Module 	Signature 	Source
0 		@0x2e6b6361 	
1 	user32.dll 	UserCallWinProcCheckWow 	
2 	user32.dll 	CallWindowProcAorW 	
3 	user32.dll 	CallWindowProcA 	
4 	nppdf32.dll 	nppdf32.dll@0x6e90 	
5 	user32.dll 	InternalCallWinProc 	
6 	user32.dll 	UserCallWinProcCheckWow 	
7 	user32.dll 	DispatchMessageWorker 	
8 	user32.dll 	DispatchMessageW 	
9 	xul.dll 	nsAppShell::ProcessNextNativeEvent 	widget/windows/nsAppShell.cpp:322
10 	xul.dll 	nsBaseAppShell::OnProcessNextEvent 	widget/xpwidgets/nsBaseAppShell.cpp:280
11 	xul.dll 	nsThread::ProcessNextEvent 	xpcom/threads/nsThread.cpp:586
12 	xul.dll 	mozilla::ipc::MessagePump::Run 	ipc/glue/MessagePump.cpp:82
13 	xul.dll 	MessageLoop::RunHandler 	ipc/chromium/src/base/message_loop.cc:201
14 	xul.dll 	MessageLoop::Run 	ipc/chromium/src/base/message_loop.cc:175
15 	xul.dll 	nsBaseAppShell::Run 	widget/xpwidgets/nsBaseAppShell.cpp:163
16 	xul.dll 	nsAppShell::Run 	widget/windows/nsAppShell.cpp:232
17 	xul.dll 	nsAppStartup::Run 	toolkit/components/startup/nsAppStartup.cpp:257
18 	xul.dll 	XREMain::XRE_mainRun 	toolkit/xre/nsAppRunner.cpp:3787
19 	xul.dll 	XREMain::XRE_main 	toolkit/xre/nsAppRunner.cpp:3864
20 	xul.dll 	XRE_main 	toolkit/xre/nsAppRunner.cpp:3940

nppdf32.dll 	9.0.0.332 	1D3B01C3A16D4F7EBBBF44A48906571D1 	Nppdf32.pdb

Comment 4

[alex_mayorga]

¡Hola Lucas!

Ended up from #2 top beta crash for Firefox 42 at https://crash-stats.mozilla.com/topcrasher/products/Firefox/versions/42.0b

I tried your steps and the URL now gives a 404 error.

Is this still a problem for you?

If not, please mark the Status below as RESOLVED WORKSFORME.

¡Gracias!
Alex

Comment 5

[Benjamin Smedberg]

Closing old bugs in the Plugins component. We aren't going to track issues in 3rd-party plugins in the Mozilla bug tracker. In addition, support for NPAPI plugins will be removed at the end of this year; for more details see the post at https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/

If there is a serious bug in Firefox, it needs to be filed in the "Core" product, "Plug-Ins" component.