Closed
Bug 141197
Opened 24 years ago
Closed 24 years ago
refcnt not initialized in nsHttpPipeline
Categories
(Core :: Networking: HTTP, defect)
Core
Networking: HTTP
Tracking
()
VERIFIED
FIXED
People
(Reporter: keeda, Assigned: darin.moz)
Details
Attachments
(1 file)
|
649 bytes,
patch
|
Details | Diff | Splinter Review |
I see lots of these on a 1.0 branch cvs debug build from earlier today. This
started after pipelining landed on the branch.
###!!! ASSERTION: illegal refcnt: 'PRInt32(mRefCnt) >= 0', file nsHttpPipeline.c
pp, line 209
###!!! ASSERTION: illegal refcnt: 'PRInt32(mRefCnt) >= 0', file nsHttpPipeline.c
pp, line 209
The trunk does not have it. This is branch only.
Trivial patch is coming up.
|
Reporter | |
Comment 1•24 years ago
|
||
|
|
||
Updated•24 years ago
|
|
|
Assignee | |
Comment 2•24 years ago
|
||
yup, i forgot about this when i landed the patch on the branch. again, i only
tested an optimized build :-(
at any rate, this is the same patch that went in on the trunk shortly after i
landed pipelining there. i'll check this in once the branch opens for checkins.
|
|
Assignee | |
Comment 3•24 years ago
|
||
fixed-on-branch
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
|
|
||
Comment 4•23 years ago
|
||
Verified per darin's comment.
Status: RESOLVED → VERIFIED
QA Contact: tever → junruh
You need to log in
before you can comment on or make changes to this bug.
Description
•