429414 - [meta] Firebug related issues in "Firefox:Session Restore"

Status: RESOLVED INVALID

(Core :: JavaScript Engine, defect)

Description

[Simon Bünzli]

Not sure whether this is the correct component (might be "Core:XPCOM" or Other "Applications:JavaScript Debugger" instead), so please move as appropriate.

There have been several reports of uncaught exceptions in nsSessionStore.js in locations where they just don't make sense, e.g.

Error: [Exception... "Component is not available"  nsresult: "0x80040111
(NS_ERROR_NOT_AVAILABLE)"  location: "JS frame ::
file:///usr/local/firefox-2.0/components/nsSessionStore.js :: sss_saveState ::
line 1753"  data: no]

where line 1753 doesn't involve any components at all (see URL). However these exceptions have almost exclusively been observed with Firebug installed (I've never managed to see them myself without that extension).

Filing this tracker in the hope of getting the attention of somebody savvy and skilled enough for solving this riddle.

Comment 1

[John J. Barton]

Setting 
disablehistory="true"
on browser XUL elements in extensions might make this problem go away.

I suppose setting this as the default then creating "enablehistory" would make the problem go away for good.

Comment 2

[Simon Bünzli]

These issues might all have been fixed (in a "we avoid doing what hurts" kind of way) by replacing toSource with JSON.stringify over in bug 407110.

Comment 3

[André Bargull [:anba]]

Firebug related bugs aren't valid anymore.