Closed Bug 634847 Opened 13 years ago Closed 9 years ago

NS_ERROR_XPC_BAD_OP_ON_WN_PROTO when trying to open addon tab

Categories

(Core :: XPConnect, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
blocking2.0 --- -

People

(Reporter: gal, Unassigned)

Details

I can't open the addon tab any more on a tracemonkey tip build. Why don't we have test coverage for this?

JavaScript error: , line 0: uncaught exception: [Exception... "Illegal operation on WrappedNative prototype object"  nsresult: "0x8057000c (NS_ERROR_XPC_BAD_OP_ON_WN_PROTO)"  location: "JS frame :: chrome://browser/content/tabbrowser.xml :: addTab :: line 1265"  data: no]

1600	    if(IS_SLIM_WRAPPER(obj) && !MorphSlimWrapper(cx, obj))
1601	        return Throw(NS_ERROR_XPC_BAD_OP_ON_WN_PROTO, cx);
1602	
1603	    XPCCallContext ccx(JS_CALLER, cx, obj, funobj, JSID_VOID, argc, JS_ARGV(cx, vp), vp);
1604	    XPCWrappedNative* wrapper = ccx.GetWrapper();
1605	    THROW_AND_RETURN_IF_BAD_WRAPPER(cx, wrapper);

            ^ we throw here

1606	
1607	    XPCNativeInterface* iface;
1608	    XPCNativeMember*    member;
1609	

(gdb) p wrapper
$3 = (struct XPCWrappedNative *) 0x0
blocking2.0: --- → ?
Mhm. Can someone else verify? I deleted my profile and rebuilt but maybe its one of those days. I will try the nightly.
We do have lots of test coverage of the addons manager being opened:
http://mxr.mozilla.org/mozilla-central/search?string=about%3Aaddons&find=test
Note that this only happened when I was trying to open the addons manager from about:home. Once I navigated to a different page it did open. I will check with a rm -rf clean build whether this persists.
Please renominate if we can reproduce, but for now this looks like it's WFM.
blocking2.0: ? → -
Can this be resolved?
WFM on the 07/17 Nightly. Removing QAwanted until enough details are available that QA could reproduce the issue.
Keywords: qawanted
Can anyone still reproduce this issue or should we just close it?
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.