Closed Bug 43106 Opened 25 years ago Closed 23 years ago

not thread-safe assertions in plugin module

Categories

(Core Graveyard :: Plug-ins, defect, P3)

Product:
Core Graveyard
Component:
Plug-ins
Platform:
x86
Windows 2000
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 156493
Milestone:
Future

People

(Reporter: sean, Assigned: serhunt)

References

(
URL
)

Details

Built from a 10am pull 6/19. The asserts don't happen all the time, but I am seeing them pretty often. ###!!! ASSERTION: nsPluginCacheListener not thread-safe: 'owningThread == NS_Cur rentThread()' ###!!! ASSERTION: nsPluginStreamListenerPeer not thread-safe: 'owningThread == N S_CurrentThread()' ###!!! ASSERTION: ns4xPluginInstance not thread-safe: 'owningThread == NS_Curren tThread()' ###!!! ASSERTION: ns4xPluginStreamListener not thread-safe: 'owningThread == NS_ CurrentThread()' ###!!! ASSERTION: ns4xPluginInstance not thread-safe: 'owningThread == NS_Curren tThread()'
Not a Netscape 6 RTM blocker. FUTURE. This bug has been marked Future because the Netscape engineer it is assigned to is overburdened.
Target Milestone: --- → Future
*** Bug 113502 has been marked as a duplicate of this bug. ***
this is being marked as a dup of request to run plug-ins in their own process/thread. These issues will be cleaned up during that work. *** This bug has been marked as a duplicate of 156493 *** *** This bug has been marked as a duplicate of 156493 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.