Closed
Bug 118225
Opened 24 years ago
Closed 19 years ago
FUM: Freeing unallocated memory
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: bstell, Assigned: jag+mozilla)
Details
Attachments
(1 file)
|
2.81 KB,
text/plain
|
Details |
purify reported this after running the page-loader test
| Reporter | ||
Comment 1•24 years ago
|
||
Comment 2•24 years ago
|
||
I'm not sure what to do with these purify bugs. Who should they be assigned to.
Bugs go nowhere assigned to me in Browser-General.
->String. Is this a dupe of jrgm's bug?
Assignee: asa → scc
Component: Browser-General → String
QA Contact: doronr → jaggernaut
Comment 4•24 years ago
|
||
scc is on sabbatical; jag, can u help?
/be
| Assignee | ||
Comment 5•24 years ago
|
||
Looking. Which of jrgm's bugs are you thinking of, dbaron?
| Reporter | ||
Comment 7•24 years ago
|
||
I am happy to help run purify. If someone would like to see the purify
build running just give me a day or so notice (compiling on Pav's system
sheep takes hours!). Once a build is ready the run takes a while (~10-60min)
but rebuilding is relatively quick.
Comment 8•23 years ago
|
||
string memory handling, over to jag, though I'll assist (string owner should be
aware of all string bugs, is my motivation for these re-assignments)
Assignee: scc → jaggernaut
Updated•19 years ago
|
Flags: blocking1.9?
Comment 9•19 years ago
|
||
Both the string code in question and the security manager code in question have gotten changed since the bug was filed. Jesse, is this even an issue?
Comment 10•19 years ago
|
||
Marking as WFM based on comment 9.
Status: NEW → RESOLVED
Closed: 19 years ago
Flags: blocking1.9?
Resolution: --- → WORKSFORME
Updated•5 years ago
|
Component: String → XPCOM
You need to log in
before you can comment on or make changes to this bug.
Description
•