Closed Bug 1013623 Opened 11 years ago Closed 11 years ago

Leak nsHttpConnectionMgr::nsConnectionHandle with pipelining enabled

Categories

(Core :: Networking: HTTP, defect)

x86_64
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla32

People

(Reporter: jruderman, Assigned: mcmanus)

References

Details

(Keywords: memory-leak, regression, testcase)

Attachments

(2 files)

Attached file testcase
1. Set user_pref("network.http.pipelining", true); 2. Run Firefox with XPCOM_MEM_LEAK_LOG=2 3. Load the testcase 4. Quit Firefox Result: trace-refcnt reports a leak of nsHttpConnectionMgr::nsConnectionHandle Based on when I started seeing this, I'm guessing it's a regression from bug 378637.
Assignee: nobody → mcmanus
Component: Networking → Networking: HTTP
jesse thanks for finding this. the issue is a latent bug made more obvious by 378637. I tried to fix it up in patch 15 of that bug, but my patch was wrong because I treated mConnection as a smart pointer when it was just a "type *".
Attachment #8426245 - Flags: review?(hurley) → review+
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla32
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: