56734 - bcJavaStubsAndProxies not thread-safe

Status: VERIFIED DUPLICATE of bug 78281

(Core Graveyard :: Java to XPCOM Bridge, defect, P3)

Description

[Jon Smirl]

**[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[0] = 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

Comment 1

[Asa Dotzler [:asa]]

setting Jon Smirl's bugs to New

Comment 2

[Akhil Arora]

hopefully george will try to find a new owner for this bug

Comment 3

[drapeau]

Ashu is taking ownership of JavaDOM bugs.  Re-assigning to him.

Comment 4

[Alexei V. Mokeev]

Changing QA contact.
Looks like this is BlackConnect(Java-to-XPCOM Bridge) bug. 
Igor, could you please look at it and change category ?  

Comment 5

[Ashu Kulkarni]

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

Comment 6

[Igor Kushnirskiy]

Closing as dup

*** This bug has been marked as a duplicate of 78281 ***

Comment 7

[Alexei V. Mokeev]

Verified DUP