Closed
Bug 397088
Opened 17 years ago
Closed 17 years ago
lots of nsIHandlerService spam in the Error Console
Categories
(Core Graveyard :: File Handling, defect)
Core Graveyard
File Handling
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: Peter6, Unassigned)
References
Details
(Keywords: regression)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a8pre) Gecko/2007092110 Minefield/3.0a8pre ID:2007092110 repro: Open FF Open errorconsole goto menu [Tools] -> [Options] select a few tabs. result: multiple Error: [Exception... "'Component is not available' when calling method: [nsIHandlerService::fillHandlerInfo]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: chrome://browser/content/preferences/applications.js :: anonymous :: line 812" data: no] Source File: chrome://browser/content/preferences/applications.js Line: 812
Comment 1•17 years ago
|
||
These are not really errors. The fact they are displayed is bug 393627
Depends on: 393627
Comment 2•17 years ago
|
||
As filed, this is a dupe of bug 393627. If you don't mind, I'll morph the bug slightly to be about the amazingly high number of nsIHandlerService::fillHandlerInfo "errors" that spam the Error Console so much that it becomes very hard to find any useful information there. I waste much time on having to deal with these and AFAIK that's not just me. If we're not going to fix bug 393627 in the near future, perhaps some workaround could be used to avoid this specific "error", since it happens too often.
Component: Preferences → General
Keywords: regression
OS: Windows XP → All
Product: Firefox → Core
QA Contact: preferences → general
Hardware: PC → All
Summary: error opening Options → lots of nsIHandlerService::fillHandlerInfo spam in the Error Console
Comment 3•17 years ago
|
||
I was actually thinking about getTypeFromExtension messages, which happen more often for me, but it looks like nsIHandlerService is generally very spam-happy.
Summary: lots of nsIHandlerService::fillHandlerInfo spam in the Error Console → lots of nsIHandlerService spam in the Error Console
Comment 4•17 years ago
|
||
(Confirming with SeaMonkey v2.0: don't know how exactly, but seeing "fillHandlerInfo" too.)
Component: General → XPConnect
QA Contact: general → xpconnect
Comment 5•17 years ago
|
||
The only reason this bug wasn't duped to bug 393627 was because it was in a different component and proposed a different solution. Moving it back into XPConnect means it no longer needs to exist.
Component: XPConnect → Preferences
Product: Core → Firefox
QA Contact: xpconnect → preferences
Updated•17 years ago
|
Component: Preferences → File Handling
Product: Firefox → Core
QA Contact: preferences → file-handling
Comment 7•17 years ago
|
||
This bug makes developing XULRunner apps very hard as we usually don't see any other error messages any more due to the limited count of console entries. And even if other errors are still in the list it's hard to find one entry between 200 others.
Comment 8•17 years ago
|
||
Fixed by bug 393627
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Comment 9•17 years ago
|
||
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a9pre) Gecko/2007102402 SeaMonkey/2.0a1pre] (nightly) (W2Ksp4) Startup: {{ Error: [Exception... "'Component is not available' when calling method: [nsIHandlerService::getTypeFromExtension]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "<unknown>" data: no] }} [Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a9pre) Gecko/2007102503 SeaMonkey/2.0a1pre] (nightly) (W2Ksp4) No error. V.Fixed.
Status: RESOLVED → VERIFIED
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•