Mozilla
Closed this issue · 6 comments
Just doing some experiments with firefox and getting this on all uses:
Failed to load script: moz-filedata:b27ca837-1d2c-4425-aa0c-fcf41f4e97b5 (nsresult = 0x80004002)
Running FireFox 8.0 on the "beta channel"
Can get some sound out of chrome 15, however it appears to be skipping (on the examples that generate random noise anyway)
Any ideas?
Cheers,
J
Hmm, could you show some code on what you're doing? I'm not exactly sure what is happening there.
Hi Jussi =)
Well im just running the tests straight out of the box, particularly the write.html example is what im interested in.
The error occurs after running the line: dev = Sink();
Failed to load script: moz-filedata:b27ca837-1d2c-4425-aa0c-fcf41f4e97b5 (nsresult = 0x80004002)
Its an odd error, and there appears to be no way in firebug to track this down to a particular line in the JS...
Hey jazzzza!
(Oh, and btw, thanks for reporting, I almost forgot)
I'm having trouble getting Firefox 8 working right now, but I'll try to investigate it further when I do (probably after some sleep).
But for now, it looks like something goes wrong in the timer initialization (sink.js uses timers from inline workers to work around the clamping of timers in background tabs). They probably changed something funky, and now I have to figure out another way to do it, meh -.- But it should actually just fall back to normal timers, so it's definitely a bug I guess.
While I'm fighting to get the beta working, could you actually try out typing this into your console in Firefox:
var timeout = Sink.doInterval(function(){ console.log('It worked'); timeout() }, 1000);and see if it produces the same error? Would help a lot :)
Cheers,
Jussi
Okay I tried it and it was what I expected it to be, looks like I'll have to file a bug for Firefox :/
Thanks!
For reference, here's the bug for firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=699633
Cheers Jussi!
Good work on isolating that issue, and.. big ups to the mozzila team who already have made a patch for this bug!
If only the IE dev team was this responsive......