Random Client Hang

ID:2336582
 
Jan 11 2018, 11:40 pm (Edited on Jan 12 2018, 3:31 am)
Resolved
Images could cause hanging in rare cases.
BYOND Version:512.1400
Operating System:Windows 7 Ultimate 64-bit
Web Browser:Chrome 64.0.3282.85
Applies to:Dream Seeker
Status: Resolved (512.1403)
This issue has been resolved.
Descriptive Problem Summary:
I've been getting reports of random hanging in ds during the game.

It finally happened to me.

Here is a stack trace from process explorer of the main thread.


ntoskrnl.exe!KeWaitForMultipleObjects+0xc0a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x712
ntoskrnl.exe!KeWaitForSingleObject+0x19f
ntoskrnl.exe!PoStartNextPowerIrp+0xbb4
ntoskrnl.exe!PoStartNextPowerIrp+0x185d
ntoskrnl.exe!PoStartNextPowerIrp+0x1ad7
byondcore.dll!??9SharedFilter@@QBE_NPAUFilterChain@@@Z+0x3e7 e
byondcore.dll!??9SharedFilter@@QBE_NPAUFilterChain@@@Z+0x682
byondcore.dll!??9SharedFilter@@QBE_NPAUFilterChain@@@Z+0x154 1
byondcore.dll!?Interpolate@FilterChain@@SAPAU1@PAU1@0M@Z+0x3 10c
byondcore.dll!?SetLinkStart@DMTextPrinter@@UAEXPBD0HHHHHHHH@ Z+0x4ca3
byondcore.dll!?SetLinkStart@DMTextPrinter@@UAEXPBD0HHHHHHHH@ Z+0x1457
byondcore.dll!?GetServerPort@DungServer@@QAEKXZ+0x5e9
byondcore.dll!?WriteBuffer@ByondHttpServerLink@@QAEXPBDJ@Z+0 x2638
byondcore.dll!?WriteBuffer@ByondHttpServerLink@@QAEXPBDJ@Z+0 x10a5
byondcore.dll!?Event_io@SocketLib@@QAEXGJ@Z+0x1f1
dreamseeker.exe+0x4f812
mfc120.dll+0x23540a
mfc120.dll+0x2350ca
mfc120.dll+0x2336ad
mfc120.dll+0x2338cf
mfc120.dll+0x133a36
USER32.dll!gapfnScSendMessage+0x332
USER32.dll!GetThreadDesktop+0xd7
USER32.dll!CharPrevW+0x13f
USER32.dll!DispatchMessageA+0xf
mfc120.dll+0x222d8c
mfc120.dll+0x1da745
mfc120.dll+0x1da9c8
dreamseeker.exe+0x3202e
mfc120.dll+0x246300
dreamseeker.exe+0x61d3e
ntdll.dll!RtlInitializeExceptionChain+0x63
ntdll.dll!RtlInitializeExceptionChain+0x36


I'll be sending you a minidump link over pm lummox.

I noticed I'm not on the most recent version, so i'll update and let you know if it happens again.
Jan 11 2018, 11:48 pm
It happened rather quickly on 512.1402, here is the stack from that.

ntoskrnl.exe!KeWaitForMultipleObjects+0xc0a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x712
ntoskrnl.exe!KeWaitForSingleObject+0x19f
ntoskrnl.exe!PoStartNextPowerIrp+0xbb4
ntoskrnl.exe!PoStartNextPowerIrp+0x185d
ntoskrnl.exe!PoStartNextPowerIrp+0x1ad7
byondcore.dll!??9SharedFilter@@QBE_NPAUFilterChain@@@Z+0x3e98
byondcore.dll!?timelib@@3UTimeLib@@A
byondcore.dll!??9SharedFilter@@QBE_NPAUFilterChain@@@Z+0x3e98
byondcore.dll!??9SharedFilter@@QBE_NPAUFilterChain@@@Z+0x682
byondcore.dll!??9SharedFilter@@QBE_NPAUFilterChain@@@Z+0x1541
byondcore.dll!?Interpolate@FilterChain@@SAPAU1@PAU1@0M@Z+0x3000
byondcore.dll!?SetLinkStart@DMTextPrinter@@UAEXPBD0HHHHHHHH@Z+0xa475
byondcore.dll!?SetLinkStart@DMTextPrinter@@UAEXPBD0HHHHHHHH@Z+0x1099
byondcore.dll!??4StyleInfo@@QAEAAU0@ABU0@@Z+0x1aa9
byondcore.dll!?LockBuffer@StringToFile@@UAEXXZ+0x1118
byondcore.dll!?WriteBuffer@ByondHttpServerLink@@QAEXPBDJ@Z+0x1055
byondcore.dll!?Event_io@SocketLib@@QAEXGJ@Z+0x1f1
dreamseeker.exe+0x4f812
mfc120.dll+0x23540a
mfc120.dll+0x2350ca
mfc120.dll+0x2336ad
mfc120.dll+0x2338cf
mfc120.dll+0x133a36
USER32.dll!gapfnScSendMessage+0x332
USER32.dll!GetThreadDesktop+0xd7
USER32.dll!CharPrevW+0x13f
USER32.dll!DispatchMessageA+0xf
mfc120.dll+0x222d8c
mfc120.dll+0x1da745
mfc120.dll+0x1da9c8
dreamseeker.exe+0x3202e
mfc120.dll+0x246300
dreamseeker.exe+0x61d3e
ntdll.dll!RtlInitializeExceptionChain+0x63
ntdll.dll!RtlInitializeExceptionChain+0x36
Jan 12 2018, 1:27 am
I looked at the minidump, but it turns out to be rather useless. The stack trace info it gave me was this:

WARNING: Stack unwind information not available. Following frames may be wrong.
00 0056ca00 5bc85842 byondcore+0x39021
01 0056ca28 5bc86701 byondcore+0x35842
02 0056ca50 5bc9cd7c byondcore+0x36701
03 0056ca68 5bc7af23 byondcore+0x4cd7c
04 0056ca90 5bc776d7 byondcore+0x2af23
05 0056cab8 5bc74269 byondcore+0x276d7
06 0056cacc 5be1f118 byondcore+0x24269
07 0056caf4 5be1db85 byondcore+0x1cf118
08 0056cb04 5be2fba1 byondcore+0x1cdb85
09 0056cb2c 0085f812 byondcore+0x1dfba1
0a 0056cb5c 5b86540a dreamseeker+0x4f812
0b 0056cc28 5b8650ca mfc120!CWnd::OnWndMsg+0x31d [f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\wincore.cpp @ 2272]
0c 0056cc48 5b8636ad mfc120!CWnd::WindowProc+0x22 [f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\wincore.cpp @ 2094]
0d 0056ccb8 5b8638cf mfc120!AfxCallWndProc+0x99 [f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\wincore.cpp @ 285]
0e 0056ccd8 5b763a36 mfc120!AfxWndProc+0x34 [f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\wincore.cpp @ 434]
0f 0056cd14 755162fa mfc120!AfxWndProcBase+0x34 [f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\afxstate.cpp @ 299] 
10 0056cd40 75516d3a user32!InternalCallWinProc+0x23
11 0056cdb8 755177d3 user32!UserCallWinProcCheckWow+0x109
12 0056ce1c 75517bda user32!DispatchMessageWorker+0x3cb
13 0056ce2c 5b852d8c user32!DispatchMessageA+0xf
14 0056ce3c 5b867f80 mfc120!AfxInternalPumpMessage+0x3e [f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\thrdcore.cpp @ 183]
15 0056ce60 5b80a745 mfc120!CWnd::RunModalLoop+0xc6 [f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\wincore.cpp @ 4644]
16 0056ce78 5b80a9c8 mfc120!CWnd::CreateRunDlgIndirect+0x3e [f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\dlgcore.cpp @ 474]
17 0056cecc 0084202e mfc120!CDialog::DoModal+0x109 [f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\dlgcore.cpp @ 633] 
18 0056f76c 5b876300 dreamseeker+0x3202e
19 0056f780 00871d3e mfc120!AfxWinMain+0x47 [f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\winmain.cpp @ 37] 
1a 0056f7cc 7718338a dreamseeker+0x61d3e
1b 0056f7d8 77709902 kernel32!BaseThreadInitThunk+0xe
1c 0056f818 777098d5 ntdll!__RtlUserThreadStart+0x70
1d 0056f830 00000000 ntdll!_RtlUserThreadStart+0x1b

Looking at just the first three frames, they don't all line up properly with instructions in either 1402 or 1401.

I'll try to get somewhere with your non-dump trace from 1402 tomorrow and see if I can tease anything out.
Jan 12 2018, 3:11 am
Looking at my downloads folder, it was 1400, not 1401, i had already updated by the time i was making the post, so i couldn't check to be sure.
Jan 12 2018, 11:00 am
Okay, knowing it's 1400 is a big help. I've finally been able to get somewhere on a trace and it appears to be an issue with images. Looking into it further.
Jan 12 2018, 1:11 pm
I think I found where the hang is occurring. How it gets into this state I can't really tell, but a simple sanity check should be able to prevent that state from causing the hang.
Jan 12 2018, 1:19 pm
Lummox JR resolved issue with message:
Images could cause hanging in rare cases.