From: Cedric B. <ced...@fr...> - 2012-02-08 10:36:14
|
On Wed, Feb 8, 2012 at 10:32 AM, Michael Blumenkrantz <mic...@gm...> wrote: > On Wed, 8 Feb 2012 10:16:05 +0100 > Mark-Willem Jansen <mar...@ho...> wrote: >> Back to the problem. The fact that valgrind finds no memory leak can mean. >> >> 1) Valgrind is not perfect and can sometimes fail to find a memory leak. >> 2) There are some pre-compiler lines in the code, different users can have >> different flags set. 3) There is no memory leak, but the code itself is >> allocating more and more memory while loading the same image over and over. >> >> Maybe the original poster can point us in the correct direction by providing >> EFL based programs he/she is using. >> >> (I fail to remember the name of the original poster.) >> >> -- >> Mark-Willem >> ---------------------------------------- >> > Date: Tue, 7 Feb 2012 21:56:24 -0500 >> > From: mic...@gm... >> > To: enl...@li... >> > CC: on...@gm... >> > Subject: Re: [E-devel] Big memory leak in e17. >> > >> > On Wed, 8 Feb 2012 12:34:38 +1000 >> > David Seikel <on...@gm...> wrote: >> > >> > > On Tue, 7 Feb 2012 21:12:04 -0500 Michael Blumenkrantz >> > > <mic...@gm...> wrote: >> > > >> > > > On Wed, 8 Feb 2012 11:59:12 +1000 >> > > > David Seikel <on...@gm...> wrote: >> > > > >> > > > > On Tue, 07 Feb 2012 03:11:40 -0500 Christopher Michael >> > > > > <cpm...@co...> wrote: >> > > > > >> > > > > > On 02/06/12 22:05, David Seikel wrote: >> > > > > > > I updated my E17 (plus EFL naturally) two days ago, just noticed >> > > > > > > that since then it's grabbed 2GBs of RAM. Think there's a leak >> > > > > > > somewhere. >> > > > > > >> > > > > > Valgrind loves you !! ;) >> > > > > >> > > > > RL hates me, not had time since then to do anything. Still >> > > > > catching up on my email, and the day is half over. Looks like >> > > > > others have picked up the scent though. >> > > > > >> > > > > Oh, and CCing duplicates to me is annoying enough, but can people >> > > > > remove the damn CC after, so I don't get the entire damn thread >> > > > > sent to me twice? sheesh >> > > > > >> > > > I was valgrinding for about 6 hours earlier and no sign of any leaks >> > > > here. >> > > >> > > You forgot to add a CC, I only got your reply twice. :-P >> > > >> > My mistake, I have rectified this issue. > No, it probably just means the leak is from a module that I'm not using. It tooks me 5s to trigger the leak. I use a normal E17 + engage + comp-scale. But the issue is in Evas, already proved that. To reproduce, just start E17 with valgrind=4, then leave. You will see your leak. -- Cedric BAIL |