Closed
Bug 283238
Opened 19 years ago
Closed 13 years ago
Audit mozilla/mailnews/base/src/nsMsgDBView.cpp
Categories
(MailNews Core :: Database, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: timeless, Unassigned)
References
()
Details
(Keywords: crash, memory-leak)
audit issues: unchecked allocs => don't crash (or leak) leaking on oom => don't leak :) else after return/return after else => drop the else and fix the indentation ns_assertion(0,...) => use ns_error
hrm, to be clear, for return after else, you need to negate the if condition, promote the return and then unindent the main block. if (foo) { statement; statement; } else return blah; => if (!foo) return blah; statement; statement;
Updated•19 years ago
|
Status: NEW → ASSIGNED
Updated•16 years ago
|
QA Contact: database
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
Comment 2•16 years ago
|
||
Gandalf, still working on this? (file in question is at: http://mxr.mozilla.org/comm-central/source/mailnews/base/src/nsMsgDBView.cpp )
Flags: wanted-thunderbird3?
Comment 3•15 years ago
|
||
didn't touch it in 4 years, so feel free to takeover. :)
Updated•15 years ago
|
Assignee: gandalf → nobody
Status: ASSIGNED → NEW
Flags: wanted-thunderbird3?
Updated•15 years ago
|
Comment 4•15 years ago
|
||
perhaps also bug 456332 and bug 460036? If so, this is likely also causing topcrashes
Severity: major → critical
Comment 5•15 years ago
|
||
(In reply to comment #0) > ns_assertion(0,...) => use ns_error More global issue, moved to bug 489505.
Comment 6•13 years ago
|
||
(In reply to comment #0) > audit issues: > 1. unchecked allocs => don't crash (or leak) > 2. leaking on oom => don't leak :) > 3. else after return/return after else => drop the else and fix the indentation > 4. ns_assertion(0,...) => use ns_error Is there anything here left to do? I skimmed the source and it looks like 1,3,4 are done. I this also done? > leaking on oom => don't leak :)
Comment 7•13 years ago
|
||
(In reply to comment #6) > I this also done? > > leaking on oom => don't leak :) The mozilla codebase has been moving to an abort-on-oom for failure, so out-of-memory should just cause the program to crash instead of merely leaking...
Comment 8•13 years ago
|
||
Resolve WFM then. :)
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Updated•13 years ago
|
Flags: wanted-thunderbird3?
You need to log in
before you can comment on or make changes to this bug.
Description
•