Frozen Application - never had this happen before

delphi package - automated exception handling
Post Reply
CarolSoprano
Posts: 1
Joined: Wed Jul 26, 2006 4:52 pm

Frozen Application - never had this happen before

Post by CarolSoprano »

Hi, I have a strange situation that I have never encountered before. I have a Delphi 5 app that is freezing on one of the PC's in a network of 10 users (it works perfectly fine on the other 9 workstations and on the server). Initially the app was giving an access violation in kernel32.dll, but now it's hanging for at least 5 minutes. It eventually opens up without exception but it is deadly slow. Anyway, here is the information:

date/time : 2006-07-26, 12:40:58, 938ms
computer name : FRONTL
user name : norma <admin>
operating system : Windows XP Service Pack 2 build 2600
system language : English
system up time : 20 hours 58 minutes
program up time : 1 minute
processors : 2x Intel(R) Pentium(R) 4 CPU 2.80GHz
physical memory : 68/246 MB (free/total)
free disk space : C: 60.79 GB F: 35.60 GB
display mode : 800x600, 32 bit
process id : $45c
allocated memory : 6.02 MB
command line : "F:\METAL POLISHERS\MEMMAINT.EXE" ALL0102030405060709
executable : MEMMAINT.EXE
exec. date/time : 2006-07-26 12:02
version : 1.0.0.0
madExcept version : 3.0b
callstack crc : $bb2ac731, $7d13b2cf, $7d13b2cf
exception number : 1
exception message : The application seems to be frozen.

main thread ($6d8):
7c90eb94 +000 ntdll.dll KiFastSystemCallRet
7c90d8ed +00a ntdll.dll NtDeviceIoControlFile
71aa150a +06a WS2HELP.dll WahReferenceContextByHandle
71ab2e64 +0a4 WS2_32.dll select
71ab2cec +083 WS2_32.dll sendto
71abf6cc +07a WS2_32.dll WSARecvFrom
71ad3039 +034 wsock32.dll recvfrom
004d350a +016 MEMMAINT.EXE GTSize32 GTForm.GTDeactivate
1219c132 +02b ACE32.DLL _axCommReq@12
0048182d +111 MEMMAINT.EXE Controls TControl.WndProc
00484376 +1d2 MEMMAINT.EXE Controls TWinControl.WndProc
00648e10 +044 MEMMAINT.EXE adsdata 4091 +17 TAdsDataSet.InternalOpen
004f043d +019 MEMMAINT.EXE Db TDataSet.DoInternalOpen
004f04ee +016 MEMMAINT.EXE Db TDataSet.OpenCursor
0064cda4 +000 MEMMAINT.EXE adsdata 8188 +0 TAdsDataSet.OpenCursor
004f03b1 +055 MEMMAINT.EXE Db TDataSet.SetActive
004f0254 +004 MEMMAINT.EXE Db TDataSet.Open
007df5a2 +04e MEMMAINT.EXE DataModule TDataModuleForm.NoteBookDMCreate
0049dcf3 +02b MEMMAINT.EXE Forms TDataModule.DoCreate
0049db4b +0df MEMMAINT.EXE Forms TDataModule.Create
004970e0 +014 MEMMAINT.EXE Forms StdWndProc
004a06b5 +031 MEMMAINT.EXE Forms TApplication.CreateForm
0082c306 +06e MEMMAINT.EXE MemMaint initialization

thread $c24:
7c90eb94 +00 ntdll.dll KiFastSystemCallRet
7c90e9be +0a ntdll.dll NtWaitForSingleObject
7c8025d5 +85 kernel32.dll WaitForSingleObjectEx
7c80253d +0d kernel32.dll WaitForSingleObject
0044ed49 +0d MEMMAINT.EXE madExcept CallThreadProcSafe
0044edb3 +37 MEMMAINT.EXE madExcept ThreadExceptFrame
>> created by main thread ($6d8) at:
187b1741 +00 axcws32.dll

thread $8d4:
7c90eb94 +00 ntdll.dll KiFastSystemCallRet
7c90e9be +0a ntdll.dll NtWaitForSingleObject
7c8025d5 +85 kernel32.dll WaitForSingleObjectEx
7c80253d +0d kernel32.dll WaitForSingleObject
0044ed49 +0d MEMMAINT.EXE madExcept CallThreadProcSafe
0044edb3 +37 MEMMAINT.EXE madExcept ThreadExceptFrame
>> created by main thread ($6d8) at:
5d0af40f +00 comctl32.dll

Can anybody help pinpoint where the problem might be? Thank you very much in advance.
Post Reply