Details
-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
None
-
Operating System: ReactOS
Platform: x86 Hardware
Description
Tested in QEMU with rev.37282, but it happened ever since Christoph_vw hack for spawning cmd windows.
To replicate:
1. Install Foxit Reader 2.3 (mfc42.dll needed);
2. Run Foxit and open any PDF file.
3. Close PDF file or close whole Foxit with PDF file opened.
To catch the error you need to break to KDBG between points 2 and 3, then:
"set condition * first always" and cont out of debugger.
Log with backtrace :
(subsystems\win32\win32k\ntuser\timer.c:172) Unable to locate timer in message queue for Window.
(ntoskrnl\mm\mm.c:141) MmAccessFault(Mode 1, Address 9eb50140)
Entered debugger on first-chance exception (Exception Code: 0xc0000005) (Page Fault)
Memory at 0x9EB50140 could not be read: Page protection violation.
kdb:> bt
Eip:
<USER32.dll:3a061 (dll/win32/user32/windows/message.c:1086 (InSendMessage@0))>
Frames:
<Foxit Reader.exe:4195c6>
<Foxit Reader.exe:405761>
<Foxit Reader.exe:3390d>
<00000001>
<Foxit Reader.exe:2fe10>
<9090c300>
Couldn't access memory at 0x864408BC!
kdb:>
Afterwards, Foxit crash window is displayed and crash report written (it gives out exactly the same info as debugger`s. If you dont set condition before closing, exception is passed and not caught.
Attachments
Issue Links
- duplicates
-
CORE-3214 Gimp 2.4.4 crash
- Resolved