Try visiting this page first with the debugger open: http://astithas.com/test/bp/index.html and then visit this one, without closing and reopening the debugger: http://astithas.com/test/a/ See that when the page changes the script list no longer contains all scripts. Screencasts that demonstrate the problem: http://www.youtube.com/watch?v=ObTdXmtbCOY http://youtu.be/8D_7lNZ2sNQ

In debugger.js, onScriptsCleared was fired sometimes after onScripts. I guess the order in which scriptsadded and scriptscleared fire isn't reliable?

Here's a log http://pastebin.mozilla.org/1498549 for: * build opened with tab on http://astithas.com/test/bp/index.html * started debugger * refreshed * location changed to http://astithas.com/test/a/

OK, I see the problem now: the newScript notifications arrive before the UI has had a chance to finish responding to the tabNavigated notification. I believe that fixing bug 723563 will indirectly fix this problem as well.

(In reply to Panos Astithas [:past] from comment #3) > OK, I see the problem now: the newScript notifications arrive before the UI > has had a chance to finish responding to the tabNavigated notification. I > believe that fixing bug 723563 will indirectly fix this problem as well. \o/

Can't reproduce this any longer, so bug 723563 must have fixed it.