Jump to content

UI hang with McAfee beta program


dimensiongt3

Recommended Posts

Posted

With latest McAfee beta program (beta.mcafee.com) uTorrent/BitTorrent UI will hang from time to time, it looks like UI thread was waiting a cs held by a synchronized network io thread:

0:010> ~0kb
ChildEBP RetAddr Args to Child
0030f4b0 77795620 7776e16a 0000024c 00000000 ntdll!KiFastSystemCallRet
0030f4b4 7776e16a 0000024c 00000000 00000000 ntdll!NtWaitForSingleObject+0xc
0030f518 7776e04d 00000000 00000000 00000000 ntdll!RtlpWaitOnCriticalSection+0x155
0030f540 0041d5cd 004c1738 0214c1e0 0214c778 ntdll!RtlEnterCriticalSection+0x152
WARNING: Stack unwind information not available. Following frames may be wrong.
0030f580 00486760 0214c1e0 004867ce 0214d268 BitTorrent+0x1d5cd
0030f5ec 0044dc3e 000d02c8 0000004e 0000001b BitTorrent+0x86760
0030f634 773749a9 00ac3f20 000d02c8 0000004e BitTorrent+0x4dc3e
0030f6b0 7737481f 00000000 00ac3f20 000d02c8 user32!UserCallDlgProcCheckWow+0x132
0030f6f8 77374a33 00000000 0000004e 0000001b user32!DefDlgProcWorker+0xa8
0030f714 7737fd72 000d02c8 0000004e 0000001b user32!DefDlgProcW+0x22
0030f740 7737fe4a 77374a11 000d02c8 0000004e user32!InternalCallWinProc+0x23
0030f7b8 77380943 00000000 77374a11 000d02c8 user32!UserCallWinProcCheckWow+0x14b
0030f7f8 77380b36 00fbde48 00ff5520 0000001b user32!SendMessageWorker+0x4b7
0030f818 74b170e1 000d02c8 0000004e 0000001b user32!SendMessageW+0x7c
... ...

0:010> !cs 004c1738
-----------------------------------------
Critical section = 0x004c1738 (BitTorrent+0xC1738)
DebugInfo = 0x00b441e8
LOCKED
LockCount = 0x1
WaiterWoken = No
OwningThread = 0x00000c10
RecursionCount = 0x1
LockSemaphore = 0x24C
SpinCount = 0x00000000

0:010> ~~[0c10]kb
ChildEBP RetAddr Args to Child
034efad0 77794810 752a7414 0000027c 000002a0 ntdll!KiFastSystemCallRet
034efad4 752a7414 0000027c 000002a0 00000000 ntdll!ZwDeviceIoControlFile+0xc
034efbd4 774d6847 0000027c 034efc14 00000001 mswsock!WSPSendTo+0x254
034efc24 004469ce 0000027c 034efda8 00000067 ws2_32!sendto+0x8c
WARNING: Stack unwind information not available. Following frames may be wrong.
034efcc8 00446efd 034efda8 00000067 021fc5e0 BitTorrent+0x469ce

If I got it right, UI won't be responding until thread 0c10 released the lock. Generally speaking a thread shouldn't hold a cs that could be waited by UI thread while performing network IO. This hang is reproducible 100% on 32-bit Vista SP2.

Posted
Can you see what the network thread is blocked on?

0:010> ~~[0c10]kb
ChildEBP RetAddr Args to Child
034efad0 77794810 752a7414 0000027c 000002a0 ntdll!KiFastSystemCallRet
034efad4 752a7414 0000027c 000002a0 00000000 ntdll!ZwDeviceIoControlFile+0xc
034efbd4 774d6847 0000027c 034efc14 00000001 mswsock!WSPSendTo+0x254
034efc24 004469ce 0000027c 034efda8 00000067 ws2_32!sendto+0x8c
WARNING: Stack unwind information not available. Following frames may be wrong.
034efcc8 00446efd 034efda8 00000067 021fc5e0 BitTorrent+0x469ce

It is this thread that is holding the critical section that the UI thread was trying to enter. Most of the times the UI can resume but few times it was frozen completely and I had to kill the process. I can provide minidump if it helps.

  • 2 weeks later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...