Closed Bug 68614 Opened 24 years ago Closed 20 years ago

non-blocking pipe implementation should not use monitors.

Categories

(Core :: XPCOM, defect)

Product:
Core
Component:
XPCOM
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX
Milestone:
Future

People

(Reporter: darin.moz, Assigned: darin.moz)

Details

(Keywords: perf) 

From bug 65146, nsPipe2 should not use java-style monitors for thread
safety.
Darin can you target this more correctly? How critical is this for 0.9?
Keywords: nsbeta1, perf
Target Milestone: --- → mozilla0.9
pushing the target milestone back.  there are more important bugs to address
at this time.
Keywords: nsbeta1
Target Milestone: mozilla0.9 → Future
This bug should have been marked fixed over a year ago when I rewrote the pipe
code.  We no longer hold the pipe monitor over large sections of code, and we
don't take advantage of its re-entrancy.  We use a granular locking strategy now
that should be good enough.  see bug 176919.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
bah, based on the summary, i shouldn't have marked this fixed.  it's really
WONTFIX (i guess).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
WONTFIX (no need to stop using monitors in the pipe code at this point)
Status: REOPENED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.