Quote: Originally Posted by xBrady
Well something is definitely up if your handle count is going that high. I let it run on my computer for 3 hours and it was still at 24.
If you turn of server log upload and let it run is the log file being added too?
I turned off server log upload and the log file is not being added to. The main window shows "Live Tracking Status: Failed". Here's a shot of the app threads if that's any help. I attached with the debugger but couldn't tell much other than whenever I paused, every thread appeared to be stopped at the same address in ntdll (FastSystemCallRet()?).
> 13276 Win32 Thread 7c90eb94 Normal 0
19360 Win32 Thread 7c90eb94 Normal 0
19704 Win32 Thread 7c90eb94 Highest 0
10636 Win32 Thread 7c90eb94 Normal 0
25408 Win32 Thread 7c90eb94 Normal 0
10556 Win32 Thread 7c90eb94 Normal 0
1272 Win32 Thread 7c90eb94 Normal 0
4048 Win32 Thread 7c90eb94 Normal 0
43168 Win32 Thread 7c90eb94 Normal 0
14660 Win32 Thread 7c90eb94 Normal 0
13460 Win32 Thread 7c90eb94 Normal 0
83804 Win32 Thread 7c90eb94 Normal 0
3436 Win32 Thread 7c90eb94 Normal 0
37824 Win32 Thread 7c90eb94 Normal 0
8640 Win32 Thread 7c90eb94 Normal 0
32204 Win32 Thread 7c90eb94 Normal 0
Example Call Stack:
> ntdll.dll!7c90eb94() FastSystemCallRet() I believe
ntdll.dll!7c90e9ab()
kernel32.dll!7c8094f2()
kernel32.dll!7c8399f3()
kernel32.dll!7c809c86()
mscorwks.dll!791d25d5()
mscorwks.dll!791d254c()
ntdll.dll!7c910732()
mscorwks.dll!791d4d50()
kernel32.dll!7c80b50b()
ntdll.dll!7c910732()
kernel32.dll!7c8399f3()
Procexplorer thread view:
Anything else I can try?