Closed Bug 390551 Opened 17 years ago Closed 17 years ago

Potential deadlock between XPCJSRuntime::mMapLockMonitor and nsComponentManagerImplMonitor

Categories

(Core :: XPConnect, defect, P2)

x86
Linux
defect

Tracking

()

RESOLVED FIXED
mozilla1.9alpha8

People

(Reporter: sayrer, Assigned: brendan)

Details

Attachments

(3 files)

The attached stack occurs reliably while running mochitest in debug mode.
diff -w coming up next.

/be
Assignee: nobody → brendan
Status: NEW → ASSIGNED
Attachment #274856 - Flags: superreview?(jst)
Attachment #274856 - Flags: review?(jst)
This was mrbkap's code. It seems we either care about thread safety only enough to take an atomic sample of wrappers to move, or we need to worry about races among threads reparenting. But only the DOM reparents, and DOM is main thread only, so there is no need to over-engineer here.

/be
Attachment #274856 - Flags: superreview?(jst)
Attachment #274856 - Flags: superreview+
Attachment #274856 - Flags: review?(jst)
Attachment #274856 - Flags: review+
Would like to get this patched. Not sure about blocking-1.9+, but I don't see a wanted-1.9 flag. What to do?

/be
Flags: blocking1.9?
Priority: -- → P2
Target Milestone: --- → mozilla1.9 M8
Flags: blocking1.9? → blocking1.9+
Fixed:

js/src/xpconnect/src/nsXPConnect.cpp 1.124

/be
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: