34.0a1 (2014-08-25), Win 8.1 x64 STR: 1. Open https://playverse-repoman-workingdir.s3.amazonaws.com/BrowserGame/index.html 2. Click Play 3. Choose the right map 4. Choose a character and wait Actual results: In the game console: "Assertion failed: undefined: abort@https://playverse-repoman-workingdir.s3.amazonaws.com/BrowserGame/index.html:411:32 assert@https://playverse-repoman-workingdir.s3.amazonaws.com/BrowserGame/index.html:417:5 addRunDependency@https://playverse-repoman-workingdir.s3.amazonaws.com/BrowserGame/index.html:817:1 FS.createPreloadedFile@https://playverse-repoman-workingdir.s3.amazonaws.com/BrowserGame/index.html:5564:9 ContentLoader</this.PushToFileToIO@https://playverse-repoman-workingdir.s3.amazonaws.com/BrowserGame/Scripts/Playverse/ContentLoader.js:24:3 ContentLoader</this.Event_TOCEntryDataBaseReadComplete@https://playverse-repoman-workingdir.s3.amazonaws.com/BrowserGame/Scripts/Playverse/ContentLoader.js:100:3 ContentLoader</this.DownloadFileWithTOCCompare/DatabaseLoadSuccess@https://playverse-repoman-workingdir.s3.amazonaws.com/BrowserGame/Scripts/Playverse/ContentLoader.js:151:4 LocalStorageManager</this.CheckAndPopulateFileFromDB/request.onsuccess@https://playverse-repoman-workingdir.s3.amazonaws.com/BrowserGame/Scripts/Playverse/LocalStorageManager.js:150:3"

Repro on FF 31

Does this assertion prevent or impeded gameplay/performance?

Yes, the game freezes and it's not able to start. This is reproducible on all platforms (Mac, Linux). I'll try on lower versions to see if this is a regression.

Thanks Paul. I'll await the results of your regression testing here before I escalate it further.

It seems to be a regression after all: Last good revision: b40296602083 (2014-05-22) First bad revision: e9b2b72f4e6c (2014-05-23) Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b40296602083&tochange=e9b2b72f4e6c Last good revision: 403e5cfa2a3c First bad revision: e08a482fcead Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=403e5cfa2a3c&tochange=e08a482fcead

It is likely to be the sec bug (1007223). Tell the game developers that now, when you pass an ArrayBuffer to decodeAudioData, the ArrayBuffer is neutered. Blink and Webkit have (or will have) the same behaviour soon. Basically, this is a problem on their side, caused by a spec evolution.

Erin, can you please escalate this? > Basically, this is a problem on their side, caused by a spec evolution. Paul, does that mean this bug report is INVALID/WONTFIX?

Yes.

Marking invalid since it's been determined that this is not a Firefox bug. Erin, I think it's still worth escalating to the developer if at all possible.

I'll let them know the info Paul outlined in comment 6. Thank you!