Open Bug 640970 Opened 13 years ago Updated 2 years ago

Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005

Categories

(Firefox :: Toolbars and Customization, defect)

x86_64
All
defect

Tracking

()

REOPENED

People

(Reporter: trappmanrhett, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows NT 5.1; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0) Gecko/20100101 Firefox/4.0

Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIObserverService.removeObserver]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://browser/content/search/search.xml ::  :: line 91"  data: no]

Reproducible: Always
Version: unspecified → Trunk
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
> *** This bug has been marked as a duplicate of bug 639093 ***
No it isn't. Re-Opening.

See also Bug 401417 Comment 65:
> I got when adding/removing the search box from the toolbar:
> Error: uncaught exception: [Exception... "Component returned failure code:
> 0x80004005 (NS_ERROR_FAILURE) [nsIObserverService.removeObserver]"  nsresult:
> "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame ::
> chrome://communicator/content/search/search.xml ::  :: line 129"  data: no]
** This is the SeaMonkey port of search.xml and the constructor/destructor is identical.
Status: RESOLVED → REOPENED
Component: General → Toolbars
Ever confirmed: true
QA Contact: general → toolbars
Resolution: DUPLICATE → ---
Status: REOPENED → NEW
Regression from Bug 396236?
Depends on: 396236
Looks like the search bar's JS object keeping the _addedObserver property even though the destructor ran. Setting _addedObserver to false from the destructor seems to avoid the problem. This affects Firefox too.
Status: NEW → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → DUPLICATE
(In reply to comment #4)
> Looks like the search bar's JS object keeping the _addedObserver property even
> though the destructor ran. Setting _addedObserver to false from the destructor
> seems to avoid the problem. This affects Firefox too.
Or you could turn _addedObserver into a field.
Re-opening and changing the dup around.
Status: RESOLVED → REOPENED
Depends on: 645062
Resolution: DUPLICATE → ---
See Also: → 618634
See Also: → 618640
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.