Closed
Bug 110820
Opened 24 years ago
Closed 24 years ago
Reduce memory allocations when painting thread pane.
Categories
(MailNews Core :: Database, defect)
MailNews Core
Database
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: Bienvenu, Assigned: Bienvenu)
Details
Attachments
(2 files)
5.47 KB,
patch
|
sspitzer
:
superreview+
|
Details | Diff | Splinter Review |
602 bytes,
patch
|
Details | Diff | Splinter Review |
It turns out that Mork guarantees the yarn it returns will be null terminated,
so we can pass them back as const char *, and the caller doesn't need to copy
them. Patch upcoming.
OS: Windows 2000 → All
QA Contact: esther → stephend
Hardware: PC → All
Assignee | ||
Comment 1•24 years ago
|
||
OK, I'm lumping a bunch of changes in this bug. I pruned away some unneeded
members in nsMsgHdr, and did some of the yarn changes I described above.
Assignee | ||
Comment 2•24 years ago
|
||
Comment 3•24 years ago
|
||
Comment on attachment 58610 [details] [diff] [review]
remove some member variables from msghdr and dbfolderinfo
sr=sspitzer
Attachment #58610 -
Flags: superreview+
Assignee | ||
Comment 4•24 years ago
|
||
Comment 5•24 years ago
|
||
r=naving
Assignee | ||
Comment 6•24 years ago
|
||
fixed
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Strange, I don't see any difference at all, really.
With the 21-04 Win32 build we have 26,248k (1st run) and 26,300k (second run)
launching mozilla.exe -mail and loading a 1,000 message IMAP Inbox, then scrolling.
On the 26-03 Win32 build we have 26,272 (1st run) and 26,248k (2nd run) using
the same steps.
But looking at the code, it's obvious you removed declarations/inits, so
Verified FIXED.
Status: RESOLVED → VERIFIED
Assignee | ||
Comment 8•24 years ago
|
||
It's really reducing the number of memory allocations - the memory was allocated
and freed right away, so it didn't contribute to bloat; it just slowed us down a
little bit.
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•