ID:2368069
 
BYOND Version:512.1423
Operating System:Windows 10 Pro 64-bit
Web Browser:Chrome 66.0.3359.139
Applies to:Dream Seeker
Status: Open

Issue hasn't been assigned a status value.
Descriptive Problem Summary:
Sometimes random textures, on turfs, turn black and as a result dreamseeker crashes.

Numbered Steps to Reproduce Problem:
Play /tg/station13

Does the problem occur:
Every time? Or how often?
Once an hour

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.)
No, but unsure what version since it's erratic

Faulting application name: dreamseeker.exe, version: 5.0.512.1423, time stamp: 0x5ae37276
Faulting module name: byondcore.dll, version: 5.0.512.1423, time stamp: 0x5ae371fb
Exception code: 0xc0000005
Fault offset: 0x00066c90
Faulting process id: 0x3e1cc
Faulting application start time: 0x01d3e8917b361806
Faulting application path: C:\Program Files (x86)\BYOND\bin\dreamseeker.exe
Faulting module path: C:\Program Files (x86)\BYOND\bin\byondcore.dll
Report Id: 11bdcfb9-0fd2-4dc9-8c61-fdf32123e299
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: dreamseeker.exe, version: 5.0.512.1423, time stamp: 0x5ae37276
Faulting module name: byondcore.dll, version: 5.0.512.1423, time stamp: 0x5ae371fb
Exception code: 0xc0000005
Fault offset: 0x00068005
Faulting process id: 0x41f58
Faulting application start time: 0x01d3e8a8f82b67f6
Faulting application path: C:\Program Files (x86)\BYOND\bin\dreamseeker.exe
Faulting module path: C:\Program Files (x86)\BYOND\bin\byondcore.dll
Report Id: dbfa96be-4598-438f-829a-ba81d59153fd
Faulting package full name:
Faulting package-relative application ID:

Not sure if wer files are handy but:
https://lithi.io/file/FMLJ.zip
No dumps seem saved for some reason.
As I feared, both of those traces are in the icon destructor. It indicates there's been heap corruption, but unfortunately there's no way to tell from a trace where that corruption is happening.

What does the client's memory use look like leading up to the crash?
I have no idea, I'll try and observe it.

Would a video of corruption and crash help in any way?
I can enable shadowplay.
There's a possibility it could be helpful. It's unlikely to help but maybe it'll reveal a pattern of some kind. More likely, however, I'd need to know a way to reproduce this in the debugger.
Some more info:

It happens usually when observing, and not normal playing the game normally.

I think this probably matters because with observing you're moving faster and seeing more atoms. So the issue is more likely to happen.