Closed
Bug 8222
Opened 25 years ago
Closed 24 years ago
identify and assess risks on all known mem leaks and free's- fix all that we can
Categories
(Core Graveyard :: Tracking, defect, P3)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: chofmann, Assigned: chofmann)
References
Details
tracking bug for memory leaks.
Assignee | ||
Updated•25 years ago
|
Assignee | ||
Updated•25 years ago
|
Depends on: 8227
Summary: identify and assess risks on all known mem leaks- fix all that we can → identify and assess risks on all known mem leaks and free's- fix all that we can
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Comment 1•24 years ago
|
||
leger is no longer @netscape. changing qa contact to component's default
QA Contact: leger → chofmann
Comment 2•24 years ago
|
||
This bug ain't really useful no more, as new leaks are reported nearly daily.
Chofmann, maybe you should consider closing this bug...
Assignee | ||
Comment 3•24 years ago
|
||
use keyword to track now...
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•