Ack, pressed 'enter' while typing up the summary --> filed not-yet-completed bug report. { http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1279576721.1279577410.18474.gz#err0 Rev3 MacOSX Leopard 10.5.8 mozilla-central opt test mochitests-1/5 on 2010/07/19 14:58:41 s: talos-r3-leopard-021 66258 ERROR TEST-UNEXPECTED-FAIL | /tests/content/smil/test/test_smilRestart.xhtml | [SimpleTest/SimpleTest.js, window.onerror] An error occurred - uncaught exception: [Exception... "An attempt was made to use an object that is not, or is no longer, usable" code: "11" nsresult: "0x8053000b (NS_ERROR_DOM_INVALID_STATE_ERR)" location: "http://mochi.test:8888/tests/content/smil/test/test_smilRestart.xhtml Line: 62"] at :0 } I think this is the same sort of thing as Bug 571016, and it needs the same test-fix that we gave that test in the final checkin for bug 552938.

looks good to me.

Comment on attachment 458474 [details] [diff] [review] workaround: add initial setCurrentTime(0) to force synchronous sample I filed Bug 580098 on the underlying bug here, and I think the patch there should fix this. I'm not landing this workaround right now, because: (a) I don't want to increase the (already sizeable) push-backlog for the code freeze tonight (b) this doesn't seem to be a super-frequent failure (and when it fails, it's easy enough to star) (c) hopefully the "real" patch on bug 580098 will be able to land very soon anyway

(In reply to comment #4) > (b) this doesn't seem to be a super-frequent failure (and when it fails, it's > easy enough to star) If this actually ends up being a frequent orange, it might be a good idea to have this bug's workaround ride along on another push (so as not to increase the push-backlog), if anyone volunteers.

pushed the workaround in comment 2 http://hg.mozilla.org/mozilla-central/rev/b816a2d20ac7 I'm leaving bug open since I dunno if this still needs a proper patch, please Daniel set it accordingly.

Thanks Marco! I'll land the "real" fix in Bug 580098 tomorrow, but we'll have less randomorange in the meantime.

Just pushed the fix for bug 580098 (& reverted the workaround from comment 7 here) in bug 580098 comment 5.