ID:2124730
 
BYOND Version:511
Operating System:Windows 10 Pro 64-bit
Web Browser:Firefox 47.0
Applies to:Dream Seeker
Status: Open

Issue hasn't been assigned a status value.
Crash in byondwin.dll
Stacktrce:
        UIAutomationCore.dll!std::_Hash,struct std::equal_to >,class std::allocator >,0> >::lower_bound(unsigned long const &)  Unknown
        UIAutomationCore.dll!CApartmentTracker::PreUninitialize(unsigned long)  Unknown
        combase.dll!NotifyInitializeSpies(int,int,unsigned long,long)   Unknown
        combase.dll!_CoUninitialize@0() Unknown
        byondwin.dll!5423e26b() Unknown
        [Frames below may be incorrect and/or missing, no symbols loaded for byondwin.dll]
        byondwin.dll!5424026a() Unknown
        byondwin.dll!542401e1() Unknown
        ntdll.dll!_LdrxCallInitRoutine@16()     Unknown
        ntdll.dll!LdrpCallInitRoutine() Unknown
        ntdll.dll!LdrShutdownProcess()  Unknown
        ntdll.dll!RtlExitUserProcess()  Unknown
        kernel32.dll!_ExitProcessImplementation@4()     Unknown
        msvcr120.dll!__crtExitProcess(int status) Line 774      C
        msvcr120.dll!doexit(int code, int quick, int retcaller) Line 666        C
        msvcr120.dll!exit(int code=0x00009750) Line 417 C
        dreamseeker.exe!003baab3()      Unknown
        kernel32.dll!@BaseThreadInitThunk@12()  Unknown
        ntdll.dll!__RtlUserThreadStart()        Unknown
        ntdll.dll!__RtlUserThreadStart@8()      Unknown


Relevant modules:
        byondwin.dll    N/A     Yes     Binary was not built with debug information.            7       5.00.511.1350   7/29/2016 1:21 PM       54190000-54342000       [11328] dreamseeker.exe
        dreamseeker.exe N/A     Yes     Binary was not built with debug information.            1       5.00.511.1350   7/29/2016 1:22 PM       00360000-0041C000       [11328] dreamseeker.exe



Might me my fault but without any information or symbols I can't resolve it; working on a library.
Because this report is for 511, I need the full version number.
Apologies, meant to mention the fact it happened in 510 as well. But the build is 1350 iirc. Actually, I might have made a mistake; the crash stack is most likely from the latest 510 build.