This is a dump of a report where the application was idle ... In background and it reported the application was frozen - incorrectly. The timeout on this was 60 seconds.
The user was actually composing a email to me at the time.
date/time : 2004-06-18 13:28
computer name : H231JYHZ0334
user name : ckelly
operating system : Windows 2000 Service Pack 3 build 2195
system language : English
system up time : 4 hours 54 minutes
program up time : 3 hours 40 minutes
physical memory : 96/255 MB (free/total)
free disk space : (C:) 15.59 GB
process id : $448
executable : ActorRostering.exe
exec. date/time : 2004-06-10 13:11
version : 3.0.3.218
madExcept version : 2.7b
exception message : The application seems to be frozen.
thread $50c:
- ???
thread $48c:
77f837b2 ntdll.dll NtWaitForMultipleObjects
thread $39c:
77f83786 ntdll.dll NtWaitForSingleObject
77e8780d kernel32.dll WaitForSingleObjectEx
77e87832 kernel32.dll WaitForSingleObject
thread $31c:
77f83786 ntdll.dll NtWaitForSingleObject
77e8780d kernel32.dll WaitForSingleObjectEx
77e87832 kernel32.dll WaitForSingleObject
thread $500:
77f83786 ntdll.dll NtWaitForSingleObject
77e8780d kernel32.dll WaitForSingleObjectEx
77e87832 kernel32.dll WaitForSingleObject
00630073 ActorRostering.exe cxStorage 1896 TcxIniFileReader.CreateLists
thread $40c:
77f837b2 ntdll.dll NtWaitForMultipleObjects
77e87ab5 kernel32.dll WaitForMultipleObjectsEx
77e8a318 kernel32.dll WaitForMultipleObjects
thread $538:
77f83197 ntdll.dll NtDelayExecution
77e87615 kernel32.dll SleepEx
77e875e6 kernel32.dll Sleep
>> created by thread $248 at:
00435ecb ActorRostering.exe madExcept ThreadExceptFrame
thread $37c:
77f83bb8 ntdll.dll NtReplyWaitReceivePortEx
>> created by thread $4fc at:
00435ecb ActorRostering.exe madExcept ThreadExceptFrame
Frozen threads checking issue.
Yes, they have had it happen several times. I think I will take the simple step and disable the frozen thread check.
It is pity the call stack info is not given for the main thread - which may have highlighted what if anything was going on. My understanding from talking to the users was that the app was just sitting in the background - eg they had starting composing an email using outlook, and the frozen thread dialog appeared from no where.
It is pity the call stack info is not given for the main thread - which may have highlighted what if anything was going on. My understanding from talking to the users was that the app was just sitting in the background - eg they had starting composing an email using outlook, and the frozen thread dialog appeared from no where.