Re: [Evolution] memory leak



Evolution often sucks up all my memory - 1 GB of RAM and another 1 GB of swap space when I delete some document element that appeared to be inside nested tables. It always happen during message composition, especially when editing and replying to a previous message.

Recent weeks, it has crashed randomly on me often, without any identifiable cause.

I know this information is not very useful, but that is all I have at this point. I'll update with more information if I manage to spend time on it and find out the problems.

-- 
Daniel Yek.


On Mon, 2006-01-30 at 14:31 -0400, Jorge Urdaneta wrote:
Well, i have some resource problems. Running evo over valgrind is very
hard, specially for me because i use it at work.

Sorry i have aborted the test. If someone wanna help, just run evolution
over valgrind until it begins to eat all the memory of the computer.
Then, close normally evo and make available to the developers the
valgrind report. It is important to have a lot of mails (i have 500+)
and open them (specially if have large attachments).

> Date: Mon, 30 Jan 2006 07:57:11 -0400
> From: Jorge Urdaneta <jorge urdaneta gmail com>
> Subject: Re: [Evolution] memory leak
> To: Veerapuram Varadhan <vvaradhan novell com>
> Cc: evolution-list gnome org
> Message-ID: <1138622233 7105 6 camel kenny ica luz ve>
> Content-Type: text/plain; charset=iso8859-1
> 
> Well, it is running with valgrind now (very slow by the way). One
> issue:
> my evolution package (shipped by Dropline Gnome) is not compiled with
> -g, so it doesn't show neither source file nor line numbers.
> 
> Dropline Gnome 2.12.2
> Evolution 2.4.2.1
> 
> Cheers

El lun, 30-01-2006 a las 02:26 -0700, Veerapuram Varadhan escribió:
> On Mon, 2006-01-30 at 05:36 +0000, Jorge Urdaneta  wrote:
> > I have used Evolution for a while but never had left it open more than
> > 12 hours.
> > 
> > Recently i have left it open by more than 6 days. The result: 793m of
> > virtual memory used, making my computer totaly unusable. I have try to
> > see what's goin on using valgrind but it report hundred of error. It
> is
> > impossible to me to see if evo actually have memory leaks or if it was
> a
> > weird and hard to reproduce bug.
> > 
> > I'm gonna let it open again by more days to see if i can reproduce the
> > issue.
> > 
> I have seen this behaviour with evolution, however, haven't let it run
> for morethan a day.
> 
> @jorge: I would appreciate a valgrind report.  If it is really big, (it
> can run into MBs), you can send a tarball of it to me.
> 
> V. Varadhan
> 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]