Using browse_rsc to output an /icon datum will often crash Dream Seeker.
[Edit: I should also add that this project is compiled in Windows 7, but runs on Ubuntu.]
I have this bit from the windows crash dialog, I'm unsure if it helps at all:
Problem signature:
Problem Event Name: APPCRASH
Application Name: dreamseeker.exe
Application Version: 4.0.496.1143
Application Timestamp: 4ffb463d
Fault Module Name: byondcore.dll
Fault Module Version: 4.0.496.1143
Fault Module Timestamp: 4ffb4605
Exception Code: c0000005
Exception Offset: 00056519
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Numbered Steps to Reproduce Problem:
1) create arbitrary /icon datum using the icon() proc
2) attempt to browse_rsc this datum as any filename
3) about 60% of the time your client crashes
Code Snippet (if applicable) to Reproduce Problem:
Just one of several browse_rsc calls that crashes DS:
proc
preload_rank_images(mob/pc/character/member)
if(isicon(src.rank_images))
for(var/r in icon_states(src.rank_images,1)) member << browse_rsc(icon(src.rank_images,r),"[md5("[src.name][r]")].png")
Expected Results:
browse_rsc sticks the icon in my BYOND cache, allowing me to use it in subsequent browse() calls.
Actual Results:
Dream Seeker crashes, and does that faded-out looking thing Windoze 7 does with an overlayed dialog box stating the program crashed.
Does the problem occur:
Every time? Or how often? Quite often, but not every time. I'd guesstimate about 60% of the time.
In other games? Don't know.
In other user accounts? Yes.
On other computers? Yes, several others are becoming crashed by the same code.
When does the problem NOT occur?
Earlier iterations of the above code snippet that did not cause a problem would browse_rsc a single-quoted cache file instead of an arbitrary runtime icon resource. I think using cache resources directly does not cause this problem.
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked?
493 was the first version I started noticing this happening, but I know there was a significant gap in my updating prior and I no longer recall the last version this wasn't happening.
Workarounds:
Don't browse_rsc an /icon, it seems.