Closed Bug 17996 Opened 25 years ago Closed 25 years ago

[PORKJOCKEY] nsCOMPtr-ize nsBrowserInstance.cpp

Categories

(SeaMonkey :: General, defect, P3)

Product:
SeaMonkey
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: waterson, Assigned: law)

Details

(Keywords: memory-leak)

nsBrowserInstance.cpp could use a good nsCOMPtr-ization when somebody gets a free minute, probably after new webshell stuff goes in...
Target Milestone: M12
Status: NEW → ASSIGNED
QA Contact: leger → law
law will need to Verify this once fix is in. Updating QA Contact.
Summary: [mlk] nsCOMPtr-ize nsBrowserInstance.cpp → [PORKJOCKEY][mlk] nsCOMPtr-ize nsBrowserInstance.cpp
Marking as porkjockey work. Bill, is this required work for M12?
Blocks: 20870
Target Milestone: M12 → M13
Resetting to M13. My priority is bug #18518 through tomorrow.
Blocks: 22176
Target Milestone: M13 → M15
Moving to M15 because I think most of this is done anyway.
Keywords: mlk
Summary: [PORKJOCKEY][mlk] nsCOMPtr-ize nsBrowserInstance.cpp → [PORKJOCKEY] nsCOMPtr-ize nsBrowserInstance.cpp
Move to M16 for now ...
Target Milestone: M15 → M16
Target Milestone: M16 → M18
Move to M21 target milestone.
Target Milestone: M18 → M21
Looking through nsBrowserInstance.cpp and nsBrowserInstance.h and it looks like it is pretty start pointer friendly. Should this bug be closed or are there some specific areas I overlooked?
This should definitely be closed. Thanks to whoever it was that scrubbed this.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
No longer blocks: 20870
No longer blocks: 22176
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.