22395 - [MLK] extensive memory usage when using composer

Status: VERIFIED FIXED

(MailNews Core :: Composition, defect, P3)

Description

[Michael Collette]

Got to writing a fairly lengthy letter in Mozilla tonight to the wishlist group
using build 1999122023.  Aside from a lot of weird cursor responces which I
entered in a previous bug report, the memory usage got WAY out of wack.  To
complete this message it took 162Meg of memory.  If that weren't bad enough this
memory was not released after the message was sent.

To get a good look at the problem bring up NT's Task Manager and a new E-Mail
message, start typing!  This same memory problem also occurs when filling in a
multi-line text box into a web site, such as this one here.

I marked the OS as all since I'm seeing the exact same effect occuring on my
Linux box.  Running build 1999122023 on Linux at the moment with this problem
hapenning there.

I thought I read a bug along these lines already posted, but upon querying
Bugzilla I couldn't find anything with "memory" or "leak" in the summary line
for message composition.  My apologies if this is a dupe.

Comment 1

[lchiang]

> This same memory problem also occurs when filling in a multi-line text box
into a web site

Reassign to beppe.

Comment 2

[Michael Collette]

While doing some follow up testing on a seperate bug (#22380) I kept an eye on
the memory usage in Composer as I typed.  There to you can watch the memory jump
skywards as you type.  This memory is not reclaimed once the Composer window is
closed either.

Comment 3

[rubydoo123]

assigning this to Kin for debugging, reassign as appropriate, updated summary

Comment 4

[Michael Collette]

Not sure who fixed this, but both mail composition and composer appear to be
properly utilizing memory at this point on NT.  I will do some follow up testing
on Linux to double check it there as well.

Changing status to FIXED.  Very sweet!

Comment 5

[sujay]

Kin, can you mark this verified fixed? thanks!

Comment 6

[sujay]

metrol, can youi please mark this VERIFIED-FIXED? thanks!

Comment 7

[sujay]

looks like this is fixed now....