Closed
Bug 1019132
Opened 10 years ago
Closed 10 years ago
"uncaught exception: 2147500033" on opening an awesometab
Categories
(Instantbird Graveyard :: Other, defect)
Instantbird Graveyard
Other
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: nhnt11, Unassigned)
References
Details
Timestamp: 03/06/14 12:04:19 am Error: uncaught exception: 2147500033
Comment 1•10 years ago
|
||
I can reproduce this. System JS : ERROR (null):0 - uncaught exception: 2147500033 This appears to be 0x80004001 (NS_ERROR_NOT_IMPLEMENTED)
Whiteboard: [1.6-blocking]
Reporter | ||
Comment 2•10 years ago
|
||
This error is coming from jsProtoHelper[1]. The call to requestRoomInfo is wrapped in a try/catch[2], but the error is still shown in the error console as uncaught. Changing the throw line to |throw Components.Exception("Not implemented.", Cr.NS_ERROR_NOT_IMPLEMENTED);| still results in the error being shown in the console, but this time with a line number and filename (and not "uncaught"). This console dump is NOT from the stats service[3], so I'm thinking it's an XPCOM related bug (or a change that we need to port). [1] - https://mxr.mozilla.org/comm-central/source/chat/modules/jsProtoHelper.jsm#197 [2] - https://mxr.mozilla.org/comm-central/source/im/components/ibConvStatsService.js#377 [3] - https://mxr.mozilla.org/comm-central/source/im/components/ibConvStatsService.js#389
Keywords: regression
Comment 3•10 years ago
|
||
Is this really blocking? Just seems like a little bit of noise in the console to me.
Updated•10 years ago
|
Whiteboard: [1.6-blocking] → [1.6-wanted]
Comment 4•10 years ago
|
||
(In reply to Patrick Cloke [:clokep] from comment #3) > Is this really blocking? Just seems like a little bit of noise in the > console to me. It's not a blocker now we know it's harmless ;)
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Component: Conversation → Other
Keywords: regression
OS: Mac OS X → All
Hardware: x86 → All
Resolution: --- → WONTFIX
Whiteboard: [1.6-wanted]
Comment 5•10 years ago
|
||
wontfix? why?
Comment 6•10 years ago
|
||
(In reply to Florian Quèze [:florian] [:flo] from comment #5) > wontfix? why? It will go away on its own if bug 981187 gets fixed. See the discussion in bug 1044109 for more details on what is happening here.
Comment 7•8 years ago
|
||
Do we want to re-evaluate now that bug 1044109 is WONTFIX?
You need to log in
before you can comment on or make changes to this bug.
Description
•