ID:2084261
 
Resolved
Images could cause hangs on the client.
BYOND Version:510.1342
Operating System:Windows 7 Ultimate 64-bit
Web Browser:Chrome 50.0.2661.94
Applies to:Dream Seeker
Status: Resolved (510.1343)

This issue has been resolved.
Descriptive Problem Summary:
Dream Seeker seems to hang a lot in games that make heavy use of images. Furthermore, it seems to mess up image animations at times.

Numbered Steps to Reproduce Problem:
1. Play a game that makes heavy use of images?
2. Dream Seeker hangs at certain points during gameplay.

Code Snippet (if applicable) to Reproduce Problem:
I can't replicate it in code, but I have provided a .dmb file or a server where it is fairly consistent.

Expected Results:
No hang.

Actual Results:
Hang!

Does the problem occur:
Every time? Or how often?
Pretty often.
In other games?
Yes.
In other user accounts?
Yes.
On other computers?
Yes.

When does the problem NOT occur?
Not sure.

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)
Did not occur before 510.1342

Workarounds:
Use version 510.1341.
Do you have crash data from the Windows event viewer?
The program dreamseeker.exe version 5.0.510.1342 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 4054
Start Time: 01d1ae51d4dc185c
Termination Time: 18
Application Path: C:\Users\Summer\Downloads\510.1342_byond\byond\bin\dreamseeker.exe
Report Id: 1d576d99-1a45-11e6-838d-bc305bdb67c8

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Hang" />
<EventID Qualifiers="0">1002</EventID>
<Level>2</Level>
<Task>101</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-05-15T02:32:27.000000000Z" />
<EventRecordID>8687</EventRecordID>
<Channel>Application</Channel>
<Computer>Summer-PC</Computer>
<Security />
</System>
- <EventData>
<Data>dreamseeker.exe</Data>
<Data>5.0.510.1342</Data>
<Data>4054</Data>
<Data>01d1ae51d4dc185c</Data>
<Data>18</Data>
<Data>C:\Users\Summer\Downloads\510.1342_byond\byond\bin\dreamseeker.exe</Data>
<Data>1d576d99-1a45-11e6-838d-bc305bdb67c8</Data>
<Binary>55006E006B006E006F0077006E0000000000</Binary>
</EventData>
</Event>


Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: dreamseeker.exe
P2: 5.0.510.1342
P3: 57363583
P4: 126d
P5: 0
P6:
P7:
P8:
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_dreamseeker.exe_2377e8112660719526463a33962a3d4954f45479_3c3c6ca3

Analysis symbol:
Rechecking for solution: 0
Report Id: 64bddb89-1996-11e6-838d-bc305bdb67c8
Report Status: 0


- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-05-14T05:40:43.000000000Z" />
<EventRecordID>8659</EventRecordID>
<Channel>Application</Channel>
<Computer>Summer-PC</Computer>
<Security />
</System>
- <EventData>
<Data />
<Data>0</Data>
<Data>AppHangB1</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>dreamseeker.exe</Data>
<Data>5.0.510.1342</Data>
<Data>57363583</Data>
<Data>126d</Data>
<Data>0</Data>
<Data />
<Data />
<Data />
<Data />
<Data />
<Data />
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_dreamseeker.exe_2377e8112660719526463a33962a3d4954f45479_3c3c6ca3</Data>
<Data />
<Data>0</Data>
<Data>64bddb89-1996-11e6-838d-bc305bdb67c8</Data>
<Data>0</Data>
</EventData>
</Event>


Report.wer:
Version=1
EventType=AppHangB1
EventTime=131076780418441784
ReportType=3
Consent=1
ReportIdentifier=64bddb88-1996-11e6-838d-bc305bdb67c8
IntegratorReportIdentifier=64bddb89-1996-11e6-838d-bc305bdb67c8
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=dreamseeker.exe
Sig[1].Name=Application Version
Sig[1].Value=5.0.510.1342
Sig[2].Name=Application Timestamp
Sig[2].Value=57363583
Sig[3].Name=Hang Signature
Sig[3].Value=126d
Sig[4].Name=Hang Type
Sig[4].Value=0
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Hang Signature 1
DynamicSig[22].Value=126d931a76d9b93e12fa38afc2f24661
DynamicSig[23].Name=Additional Hang Signature 2
DynamicSig[23].Value=ee29
DynamicSig[24].Name=Additional Hang Signature 3
DynamicSig[24].Value=ee29d452de88bbc0364eef9aca43c1e8
DynamicSig[25].Name=Additional Hang Signature 4
DynamicSig[25].Value=126d
DynamicSig[26].Name=Additional Hang Signature 5
DynamicSig[26].Value=126d931a76d9b93e12fa38afc2f24661
DynamicSig[27].Name=Additional Hang Signature 6
DynamicSig[27].Value=ee29
DynamicSig[28].Name=Additional Hang Signature 7
DynamicSig[28].Value=ee29d452de88bbc0364eef9aca43c1e8
UI[3]=Dream Seeker is not responding
UI[4]=Windows can check online for a solution. If you close the program, you might lose information.
UI[5]=Check for a solution and close the program
UI[6]=Check for a solution and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\BYOND\bin\dreamseeker.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Program Files\Bitdefender\Antivirus Free Edition\avc3\avc3_sig_358\avcuf32.dll
LoadedModule[5]=C:\Program Files (x86)\BYOND\bin\byondwin.dll
LoadedModule[6]=C:\Program Files (x86)\BYOND\bin\byondcore.dll
LoadedModule[7]=C:\Program Files (x86)\BYOND\bin\byondext.dll
LoadedModule[8]=C:\Windows\syswow64\USER32.dll
LoadedModule[9]=C:\Windows\syswow64\GDI32.dll
LoadedModule[10]=C:\Windows\syswow64\LPK.dll
LoadedModule[11]=C:\Windows\syswow64\USP10.dll
LoadedModule[12]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[13]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[14]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[15]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[16]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[17]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[18]=C:\Program Files (x86)\BYOND\bin\MSVCR120.dll
LoadedModule[19]=C:\Windows\system32\WSOCK32.dll
LoadedModule[20]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[21]=C:\Windows\syswow64\NSI.dll
LoadedModule[22]=C:\Windows\system32\WINMM.dll
LoadedModule[23]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[24]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[25]=C:\Program Files (x86)\BYOND\bin\MSVCP120.dll
LoadedModule[26]=C:\Windows\system32\VERSION.dll
LoadedModule[27]=C:\Windows\system32\MSIMG32.dll
LoadedModule[28]=C:\Program Files (x86)\BYOND\bin\mfc120.dll
LoadedModule[29]=C:\Windows\syswow64\ole32.dll
LoadedModule[30]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[31]=C:\Windows\syswow64\IMM32.dll
LoadedModule[32]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[33]=C:\Windows\system32\UxTheme.dll
LoadedModule[34]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[35]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll
LoadedModule[36]=C:\Windows\system32\d3dx9_43.dll
LoadedModule[37]=C:\Windows\system32\RICHED32.DLL
LoadedModule[38]=C:\Windows\system32\RICHED20.dll
LoadedModule[39]=C:\Windows\system32\dwmapi.dll
LoadedModule[40]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.DLL
LoadedModule[41]=C:\Windows\system32\NLAapi.dll
LoadedModule[42]=C:\Windows\system32\napinsp.dll
LoadedModule[43]=C:\Windows\system32\pnrpnsp.dll
LoadedModule[44]=C:\Windows\System32\mswsock.dll
LoadedModule[45]=C:\Windows\system32\DNSAPI.dll
LoadedModule[46]=C:\Windows\System32\winrnr.dll
LoadedModule[47]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[48]=C:\Windows\system32\WINNSI.DLL
LoadedModule[49]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[50]=C:\Windows\system32\rasadhlp.dll
LoadedModule[51]=C:\Windows\System32\wshtcpip.dll
LoadedModule[52]=C:\Windows\system32\d3d9.dll
LoadedModule[53]=C:\Windows\system32\d3d8thk.dll
LoadedModule[54]=C:\Windows\system32\nvd3dum.dll
LoadedModule[55]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[56]=C:\Windows\system32\nvspcap.dll
LoadedModule[57]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[58]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[59]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[60]=C:\Windows\system32\WINHTTP.dll
LoadedModule[61]=C:\Windows\system32\webio.dll
LoadedModule[62]=C:\Windows\system32\nvapi.dll
LoadedModule[63]=C:\Windows\system32\profapi.dll
LoadedModule[64]=C:\Windows\system32\powrprof.dll
LoadedModule[65]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[66]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[67]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[68]=C:\Windows\SysWOW64\OLEACC.dll
LoadedModule[69]=C:\Windows\syswow64\iertutil.dll
LoadedModule[70]=C:\Windows\syswow64\urlmon.dll
LoadedModule[71]=C:\Windows\syswow64\WININET.dll
LoadedModule[72]=C:\Windows\syswow64\Normaliz.dll
LoadedModule[73]=C:\Windows\system32\SXS.DLL
LoadedModule[74]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[75]=C:\Windows\system32\rsaenh.dll
LoadedModule[76]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[77]=C:\Program Files (x86)\BYOND\bin\fmodex.dll
LoadedModule[78]=C:\Windows\system32\MSACM32.dll
LoadedModule[79]=C:\Windows\System32\MMDevApi.dll
LoadedModule[80]=C:\Windows\System32\PROPSYS.dll
LoadedModule[81]=C:\Windows\system32\AUDIOSES.DLL
FriendlyEventName=Stopped responding and was closed
ConsentKey=AppHangXProcB1
AppName=Dream Seeker
AppPath=C:\Program Files (x86)\BYOND\bin\dreamseeker.exe
ReportDescription=A problem caused this program to stop interacting with Windows.


I have two different versions of BYOND in different locations, but this happened even when I updated my normal version (which is what prompted me to have two versions, because Dream Seeker kept crashing). Dunno why Report.wer is reporting the wrong location.
Those are hangs, not crashes.
https://dl.dropboxusercontent.com/u/51176364/scratch.zip

Those hangs occur for me too, I made a test case to reproduce them, it occurs on the second click of Crash verb.

Seems to be completely client sided, the server doesn't hang just the clients.
Well, it hangs forever, or at least an undisclosed long amount of time, so I consider that a crash. Perhaps Rotem12's test case will work better, as I didn't know exactly what was causing it, but Rotem12 seems to have it down.
In response to Kamuna
Kamuna wrote:
Well, it hangs forever, or at least an undisclosed long amount of time, so I consider that a crash.

A hang is not a crash. They're completely different phenomena and the distinction is important.
Also having lots of hangs/crashes since the last update.
Indeed a hang is not a crash, and I'm sure the distinction is important.
Descriptive Problem Summary:
(Reporting this for one of our admins, niknakflak.)

Client hangs in 1342 shortly after joining a game.

Doesn't happen in 1341.

Its a Core i7-5500U processor so this *might* be related to that intel change.
In response to MrStonedOne
Its a Core i7-5500U processor so this *might* be related to that intel change.

Man, whoever suggested that was an idiot. I've got a report of a similar hang by a user:

Windows 10 - MS edge 20.10240.16384.0

Intel 2 quad cpu 2.83Ghz Q9550

Intalled memory (8.00GB)

DirectX Version: DX12

NVIDIA GeForce GTX760 (6084MB)

Version: 10.18.13.5900

Weird thing is that he's using a IQuad, not an I-series.

So... It might be related to the Adapter selection change, and it might be related to something else.
In response to MrStonedOne
The question I'd be asking them is whether the system has a secondary graphics processor or not, I'm hearing bits and pieces now too and the common thread I'm finding is they have systems with Intel chip for graphics. But like I said I haven't talked to anyone directly about it so I don't have any solid details to report back outside of a 'maybe'.

It does seem to be something with the adapter change though, and a lot of it is from laptops.
In response to MrStonedOne
We've had a number of people report the same problem to us exclusively in 1342
In response to MrStonedOne
I think this is the image bug.
In response to MrStonedOne
Same bug here.

Win 10
i7 4790k
2x GTX 970 in SLI
16GB RAM 1600MHz
In response to MrStonedOne
Same issue here.
Win 7
AMD Athlon X4 620, 2.60 GHz
ATI Radeon HD 4800 Series
8GB RAM
Lummox JR resolved issue with message:
Images could cause hangs on the client.
:)