🚀 go-pugleaf

Currently, my company is using the Adobe Reader ActiveX Control in a .net 2.0 application to view PDF documents. We have found that the updated Adobe Reader 9 version crashes our application; versions prior to 9 do not exhibit this issue. In order to diagnose the issue we created a very simple application which exercises the issue within the ActiveX control. Below is the stack trace which is generated when the application fails. Does anyone know how I may obtain developer assistance with this issue?

0:000> !dumpstack
OS Thread Id: 0x13c4 (0)
Current frame: bib!BIBInitialize4+0x22e9
ChildEBP RetAddr Caller,Callee
0012fad0 0700614c bib!BIBInitialize4+0x2399, calling bib!BIBInitialize4+0x228d
0012faf4 070064db bib!BIBInitialize4+0x2728, calling bib!BIBInitialize4+0x231d
0012fb18 07007754 bib!BIBInitialize4+0x39a1, calling bib+0x111b
0012fb24 0700f8f5 bib!BIBLockSmithAssertNoLocksImpl+0x5625
0012fb2c 07006899 bib!BIBInitialize4+0x2ae6
0012fb40 0700d903 bib!BIBLockSmithAssertNoLocksImpl+0x3633, calling bib!BIBInitialize4+0x295f
0012fb84 070068f2 bib!BIBInitialize4+0x2b3f, calling bib!BIBLockSmithAssertNoLocksImpl+0x357c
0012fb8c 7c9011a7 ntdll!LdrpCallInitRoutine+0x14
0012fbac 7c923f31 ntdll!LdrShutdownProcess+0x14f, calling ntdll!LdrpCallInitRoutine
0012fbf0 7c910945 ntdll!RtlAcquirePebLock+0x28
0012fbf4 7c91094e ntdll!RtlAcquirePebLock+0x31, calling ntdll!_SEH_epilog
0012fc30 7c81cd76 KERNEL32!_ExitProcess+0x42, calling ntdll!LdrShutdownProcess
0012fc4c 77557227 ole32!CoWaitForMultipleHandles+0xcf, calling ole32!CCliModalLoop::BlockFn
0012fc58 775571fc ole32!CoWaitForMultipleHandles+0x128, calling ole32!CCliModalLoop::~CCliModalLoop
0012fc64 77557211 ole32!CoWaitForMultipleHandles+0x14a, calling ole32!__security_check_cookie
0012fcc0 79f752f0 mscorwks!NT5WaitRoutine+0x51, calling ole32!CoWaitForMultipleHandles
0012fcc8 79f73b72 mscorwks!CCLROnEventManager::ProcessEvent+0x122, calling mscorwks!_EH_epilog3
0012fce0 79f75232 mscorwks!MsgWaitHelper+0xa5, calling mscorwks!NT5WaitRoutine
0012fcfc 79f73b72 mscorwks!CCLROnEventManager::ProcessEvent+0x122, calling mscorwks!_EH_epilog3
0012fd00 79f73b3d mscorwks!ProcessEventForHost+0x2a, calling mscorwks!CCLROnEventManager::ProcessEvent
0012fd24 7c81cdee KERNEL32!ExitProcess+0x14, calling KERNEL32!_ExitProcess
0012fd38 79fd9e8f mscorwks!SafeExitProcess+0x157, calling KERNEL32!ExitProcess
0012fd74 79e744f5 mscorwks!Thread::EnterRuntime+0x1f, calling ntdll!RtlSetLastWin32Error
0012fd80 79ed985a mscorwks!Thread::DoAppropriateWaitWorker+0x2ad, calling mscorwks!_EH_epilog3
0012fdec 79ed985a mscorwks!Thread::DoAppropriateWaitWorker+0x2ad, calling mscorwks!_EH_epilog3
0012fdf0 79ed96c4 mscorwks!Thread::DoAppropriateWait+0x40, calling mscorwks!Thread::DoAppropriateWaitWorker
0012fe04 79ed96de mscorwks!Thread::DoAppropriateWait+0x5a, calling mscorwks!_SEH_epilog4
0012fe3c 79ed96de mscorwks!Thread::DoAppropriateWait+0x5a, calling mscorwks!_SEH_epilog4
0012fe40 79ed9a62 mscorwks!CLREvent::WaitEx+0xf7, calling mscorwks!Thread::DoAppropriateWait
0012fe58 79e78994 mscorwks!CLREvent::WaitEx+0x11c, calling mscorwks!_EH_epilog3
0012fe98 79e78994 mscorwks!CLREvent::WaitEx+0x11c, calling mscorwks!_EH_epilog3
0012fe9c 79e78944 mscorwks!CLREvent::Wait+0x17, calling mscorwks!CLREvent::WaitEx
0012fea8 79e7904f mscorwks!CLRException::HandlerState::CleanupTry+0x16, calling mscorwks!GetCurrentSEHRecord
0012febc 79f75175 mscorwks!CorExitProcess+0x32d, calling mscorwks!CLRException::HandlerState::CleanupTry
0012fec0 79e71b90 mscorwks!_EH_epilog3_catch_GS+0xa, calling mscorwks!__security_check_cookie
0012fec4 79f75187 mscorwks!CorExitProcess+0x420, calling mscorwks!_EH_epilog3_catch_GS
0012fef8 79e734c4 mscorwks!ClrFlsSetValue+0x57, calling mscorwks!_EH_epilog3
0012ff20 79e734c4 mscorwks!ClrFlsSetValue+0x57, calling mscorwks!_EH_epilog3
0012ff24 79fd8717 mscorwks!ClrFlsClearThreadType+0x17, calling mscorwks!ClrFlsSetValue
0012ff30 79f750af mscorwks!EEShutDown+0xc0, ca