Game Music Crashes Safari (Desktop)

Not sure where to post this really, I don't know if it's a bug with Safari, Construct or something we've done. It's an error that only occurs in Safari (desktop); basically when the music starts on our latest Ludum Dare game, then the browser crashes. It all works fine on Chrome and Firefox. Don't know what to do really, we just added music to the game and then played it.

Anyone else had these issues? The Safari error message is below if that helps.

Link to the game is on our Ludum Dare page here:

ludumdare.com/compo/ludum-dare-27

-------------------------------------------------------------------

ERROR REPORT

-------------------------------------------------------------------

Process:        WebProcess [280]

Path:

/System/Library/StagedFrameworks/Safari/WebKit2.framework/WebProcess.app/Contents/MacOS/WebProcess

Identifier:      com.apple.WebProcess

Version:        8536 (8536.26.17)

Build Info:      WebKit2-7536026017000000~1

Code Type:       X86-64 (Native)

Parent Process: ??? [1]

User ID:        501

Date/Time:       2013-09-11 09:44:56.377 +0100

OS Version:      Mac OS X 10.8.2 (12C60)

Report Version: 10

Interval Since Last Report:          5090769 sec

Crashes Since Last Report:           101

Per-App Interval Since Last Report: 29 sec

Per-App Crashes Since Last Report:   1

Anonymous UUID: 1A1C50AD-09B8-A3A4-432B-2DFC4AC79D43

Crashed Thread: 16 Audio Decoder

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x00000000bbadbeef

VM Regions Near 0xbbadbeef:

-->

     __TEXT                 000000010ca9f000-000000010caa0000 [ 4K]

r-x/rwx SM=COW

/System/Library/StagedFrameworks/Safari/WebKit2.framework/WebProcess.app/Contents/MacOS/WebProcess

Application Specific Information:

Bundle controller class:

BrowserBundleController

If Safari crashes, it's definitely a Safari bug and not a Construct 2 bug. You should report it to Apple. Alternatively perhaps there's a problem with the encoding of some of your audio files (since it says the crashed thread was "Audio Decoder"). Re-encoding them or using different settings might help.

Ashley I get your point Ashley, but we can't stop waiting for Safari to fix their issues. You can't say to a customer that their browser is the issue, to the customer if it doesn't work right away, it's Broken, ant that's a Lost customer, they won't get back, and they definitely won't download another browser. The customer doesn't know how to use computers, so if it doesn't work, they won't dig in and find a fix. They are not geeks, they are not nerds.

One needs to support their browsers, whatever they use.

There must be support to Safari with workarounds, like many developers did/do supporting IE, specially now, specially at these point in history that Safari /iPad is the largest user base of customers right now.

ghost - in this case there appears to be nothing we can do. The audio file is passed to Safari and it crashes decoding it. It's not like there's some Javascript we can change to work around that.