Forum
Please
Log In
to post a new message or reply to an existing one. If you are not registered, please
register.
NOTE: Some forums may be read-only if you are not currently subscribed to
our technical support services.
|
Subject |
Author |
Date |
|
|
Timothy Anderson
|
Oct 14, 2008 - 10:53 PM
|
I’m trying to track down the UI thread locking up on my application. Here’s a quick debug dump: STACK_TEXT:
0012f2ac 7c827d0b 7c83d236 0000031c 00000000 ntdll!KiFastSystemCallRet
0012f2b0 7c83d236 0000031c 00000000 00000000 ntdll!NtWaitForSingleObject+0xc
0012f2ec 7c83d281 0000031c 00000004 00000001 ntdll!RtlpWaitOnCriticalSection+0x1a3
0012f30c 7c82f20c 7c8877a0 00000000 0012f408 ntdll!RtlEnterCriticalSection+0xa8
0012f340 7c82f336 00000000 00000000 0012f388 ntdll!LdrLockLoaderLock+0x133
0012f3bc 7c82f2a3 00000001 00000001 00000000 ntdll!LdrGetDllHandleEx+0x94
0012f3d8 77e65185 00000001 00000000 0012f440 ntdll!LdrGetDllHandle+0x18
0012f424 77e6528f 0012f440 0012f9dc 0012fa38 kernel32!GetModuleHandleForUnicodeString+0x20
0012f89c 77e65155 00000001 00000002 7ffdfc00 kernel32!BasepGetModuleHandleExW+0x17f
0012f8b4 77e64769 7ffdfc00 00000000 7822716b kernel32!GetModuleHandleW+0x29
0012f8c0 7822716b 781df614 0012f9fc 10010475 kernel32!GetModuleHandleA+0x2d
0012f8cc 10010475 00000000 0012f9dc 0012fa38 mfc80!CDC::GetLayout+0xe [f:\sp\vctools\vc7libs\ship\atlmfc\src\mfc\wingdi.cpp @ 698]
WARNING: Stack unwind information not available. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 ProfUIS282m!CExtMemoryDC::__InitMemoryDC+0xa5 I’m trying to remember exactly what I was doing with this but I believe I started up another UI thread in order to have a hovering "cancel" box above our main application with it’s own UI thread running normally. I’m going to keep digging on this, but has anyone seen anything like this before? The main problem is after the cancel box goes away the main application is simply locked up and has to be killed. This unfortunately only happens "every now and then." It’s obviously driving me insane. Any hints would be fabu.
|
|
|
Technical Support
|
Oct 15, 2008 - 11:31 AM
|
The above call stack gives us very little to understand what is wrong. We can guess that you are using a non-multi-thread library from different threads but the GDI subsystem is not multithreaded.
Besides, please try to remember when this problem appeared for the first time. It is always possible to comment out this and that part of code in order to find out what causes the problem.
|
|