Closed
Bug 39350
Opened 24 years ago
Closed 24 years ago
GC_LEAK_DETECTOR and the PRThread structure
Categories
(NSPR :: NSPR, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
4.0.2
People
(Reporter: wtc, Assigned: wtc)
Details
Attachments
(1 file)
1.77 KB,
patch
|
Details | Diff | Splinter Review |
It turns out that it is not safe to allocate the thread object on the stack, because we assign to this object before the GC can learn about this thread. We'll just leak thread objects instead.
Assignee | ||
Comment 1•24 years ago
|
||
Assignee | ||
Updated•24 years ago
|
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Target Milestone: --- → 4.0.1
Assignee | ||
Comment 2•24 years ago
|
||
Checked in the patch on the main trunk. /cvsroot/mozilla/nsprpub/pr/src/misc/prthinfo.c, revision 3.5 /cvsroot/mozilla/nsprpub/pr/src/threads/combined/pruthr.c, revision 3.26 Checked in the patch on the NSPRPUB_RELEASE_4_0_BRANCH. /cvsroot/mozilla/nsprpub/pr/src/misc/prthinfo.c, revision 3.4.8.1 /cvsroot/mozilla/nsprpub/pr/src/threads/combined/pruthr.c, revision 3.22.6.1 Checked in the patch on the NSPRPUB_CLIENT_BRANCH. /cvsroot/mozilla/nsprpub/pr/src/misc/prthinfo.c, revision 3.4.22.1 /cvsroot/mozilla/nsprpub/pr/src/threads/combined/pruthr.c, revision 3.22.20.1
Assignee | ||
Updated•24 years ago
|
Target Milestone: 4.0.1 → 4.0.2
You need to log in
before you can comment on or make changes to this bug.
Description
•