**[c++]hasRetval: 0 --nsresult bcJavaMarshalToolkit::UnMarshal --[c++] bcJavaMarshalToolkit::UnMarshalElement we have an interface 0 oid --[c++] bcJavaStubsAndProxies::GetInterface --[java] ProxyFactory.getInterface org.mozilla.xpcom.IID@47267425-667b-11d4-b7dc -00a0cc3e7072 --[java]org.mozilla.xpcom.Utilities.callMethodByIndex 1 7 --[java]callMethodByIndex args = null --[java] org.mozilla.xpcom.Utilities.callMethodByIndex method null --[java] Utilities.callMethodByIndex method finishednull --[c++] bcXPCOMProxy::Release 0 --bcJavaComponentFactory::CreateInstance ###!!! ASSERTION: bcJavaStubsAndProxies not thread-safe: 'owningThread == NS_Cur rentThread()', file d:\cvs\mozilla\xpcom\base\nsDebug.cpp, line 490
setting Jon Smirl's bugs to New
Status: UNCONFIRMED → NEW
Ever confirmed: true
hopefully george will try to find a new owner for this bug
Assignee: akhil.arora → drapeau
Ashu is taking ownership of JavaDOM bugs. Re-assigning to him.
Assignee: drapeau → ashuk
Changing QA contact. Looks like this is BlackConnect(Java-to-XPCOM Bridge) bug. Igor, could you please look at it and change category ?
QA Contact: rajendra.pallath → avm
Hello Igor, This Bug is in BlackConnect and relates to thread-safety. I believe that you have this feature working by now, and so this bug might just need to be closed. Anyways, I am assigning it to you since it belongs in the BlackConnect module. thnx. _Ashu
Assignee: ashuk → idk
Component: Java APIs for DOM → Java to XPCOM Bridge
Closing as dup *** This bug has been marked as a duplicate of 78281 ***
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.