ID:1312554
 
Resolved
Sound environment and echo settings together could cause a crash in some cases.
BYOND Version:499.1197
Operating System:Windows 7 Pro 64-bit
Web Browser:Chrome 28.0.1500.63
Applies to:Dream Seeker
Status: Resolved (499.1199)

This issue has been resolved.
proc/build_random_echo()
var/list/echo[18]
echo[1] = rand(-10000, 1000) //direct
echo[2] = rand(-10000, 0) //direct hf
echo[3] = rand(-10000, 1000) //room
echo[4] = rand(-10000, 0) //room hf
echo[5] = rand(-10000, 0) //obstruction
echo[6] = rand(0, 100) * 0.01 //obstruction lf ratio
echo[7] = rand(-10000, 0) //occlusion
echo[8] = rand(0, 100) * 0.01 //occlusion lf ratio
echo[9] = rand(0, 100) * 0.1 //occlusion room ratio
echo[10] = rand(0, 100) * 0.1 //occlusion direct ratio
echo[11] = rand(-10000, 0) //exclusion
echo[12] = rand(0, 100) * 0.01 //exclusion lf ratio
echo[13] = rand(-10000, 0) //outside volume hf
echo[14] = rand(0, 100) * 0.1 //doppler factor
echo[15] = rand(0, 100) * 0.1 //rolloff factor
echo[16] = rand(0, 100) * 0.1 //room roll off factor
echo[17] = rand(0, 100) * 0.1 //air absorption factor
echo[18] = 1 | 2 | 4 //flags

return echo

mob/verb/test2()
var/sound/dry = sound('clap.ogg')
var/sound/wet = sound('clap.ogg')

wet.environment = 1
wet.echo = build_random_echo()

src << dry
sleep(5)
src << wet


Compile this code
Run project
Click test2()
Click the "X" button on the window to close dream seeker. Dreamseeker will crash.
Lummox JR changed status to 'Unverified'
I can't reproduce this. If you can get some crash details that could help.
Let me know how to do that and I'll gladly do it.
You should be able to get crash details from Windows when a crash happens. It should tell you the module and offset where the crash occurred. When you get that I'll need to know if you're on 1197 or 1198, as well.
I wish I was more help... but there are no details: http://i.imgur.com/eE7KdRP.png

I tested on on 499.1197 and 499.1198
I've seen other users who had an option to view crash details. I'm not sure why it doesn't show for you but I'm not as familiar with how Windows 7 handles this stuff.
Faulting application name: dreamseeker.exe, version: 4.0.499.1198, time stamp: 0x51d458b3
Faulting module name: fmodex.dll, version: 0.4.32.1, time stamp: 0x4c7406a3
Exception code: 0xc0000005
Fault offset: 0x00089294
Faulting process id: 0x814
Faulting application start time: 0x01ce782ab2dd0b9c
Faulting application path: C:\Program Files (x86)\BYOND\bin\dreamseeker.exe
Faulting module path: C:\Program Files (x86)\BYOND\bin\fmodex.dll
Report Id: f5127395-e41d-11e2-ac96-20cf30e81171

And here's another with a different fault offset

Faulting application name: dreamseeker.exe, version: 4.0.499.1198, time stamp: 0x51d458b3
Faulting module name: fmodex.dll, version: 0.4.32.1, time stamp: 0x4c7406a3
Exception code: 0xc0000005
Fault offset: 0x0003bdb5
Faulting process id: 0x814
Faulting application start time: 0x01ce782ab2dd0b9c
Faulting application path: C:\Program Files (x86)\BYOND\bin\dreamseeker.exe
Faulting module path: C:\Program Files (x86)\BYOND\bin\fmodex.dll
Report Id: f46f7a72-e41d-11e2-ac96-20cf30e81171
If you want to know for the future, its in:
Event Viewer -> Windows Logs -> Application
I can't trace it from FMod, but I was able to reproduce this in release mode so I'll see what I can find.
Lummox JR resolved issue with message:
Sound environment and echo settings together could cause a crash in some cases.