Closed
Bug 56728
Opened 24 years ago
Closed 23 years ago
bcJavaComponentFactory not thread-safe
Categories
(Core Graveyard :: Java to XPCOM Bridge, defect, P3)
Core Graveyard
Java to XPCOM Bridge
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jonsmirl, Assigned: blackconnect)
Details
Attachments
(1 file)
|
2.38 KB,
patch
|
Details | Diff | Splinter Review |
bcJavaComponentFactory is triggering the not thread-safe assert. This component needs to be checked for thread saftey and then switch to NS_IMPLS_THREADSAFE_ISUPPORT when ready. **[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 ###!!! ASSERTION: bcJavaComponentFactory not thread-safe: 'owningThread == NS_Cu rrentThread()', file d:\cvs\mozilla\xpcom\base\nsDebug.cpp, line 490
|
||
Comment 1•24 years ago
|
||
setting Jon Smirl's bugs to New
Status: UNCONFIRMED → NEW
Ever confirmed: true
|
Assignee | |
Updated•23 years ago
|
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 2•23 years ago
|
||
|
|
Assignee | |
Comment 3•23 years ago
|
||
bcJavaComponentFactory is thread safe. The fix is just changing NS_IMPL_ISUPPORTS1 to NS_IMPL_THREADSAFE_ISUPPORTS1 I am closing the bug as fixed
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
|
||
Updated•10 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•