[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    2_2_BRANCH commits.
From:       Don Sanders <sanders () trolltech ! com>
Date:       2001-08-22 20:12:05
[Download RAW message or body]

Hi,

I'm considering committing the recent memory leak/excessive 
memory pooling fixes to the KDE_2_2_BRANCH. I committed 
them to HEAD several days ago.

I've been testing them for a few days. The kmfoldertree.cpp 
changes can't really go wrong I think. I can't see anything 
wrong with the kmmainwin.* changes, and I've been testing 
them for several days, so I think they are probably ok.

But I don't want to mess things up, so I thought I'd asked 
for your opinion. We're currently wasting about a meg of 
ram for every 150 folder changes. Do you think it's 
worthwhile to commit?

Here are the changes I speak of:

http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdenetwork/kmail/kmfoldertree.cpp.diff?r1=1.134&r2=1.135
http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdenetwork/kmail/kmmainwin.cpp.diff?r1=1.350&r2=1.351
http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdenetwork/kmail/kmmainwin.h.diff?r1=1.93&r2=1.94

Yeah, double checking it looks pretty harmless.

Don.
_______________________________________________
Kmail Developers mailing list
Kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail

[prev in list] [next in list] [prev in thread] [next in thread]