Re: [e-users] tracking down memory issue

[Conrad Knight]

> From: Cedric BAIL 

> As for tracking memory leak
> the right tool this day is valgrind. It is going to slow down the
> tracked software quite a lot !
> enlightenment_start -massif -display :1.0

Actually, the slowing wasn't too bad, and it was easier to catch it at
the right moment running it directly this way in my regular X session.
A few days of trial-and-error produced a massif output file with the
run-away memory problem.

> You can open
> that file using massif-visualizer and look at what is constantly
> increasing.

I'm not sure what i'm looking at, but the main culprit seems to be
"e_main.c:1062" with 1.1GiB. Unless i'm reading it backward, in which
case it's something in libX11.so.6.3.0. At the same time, there's a
second 1.0GiB pile of "e_main.c:1062" with
"_ecore_x_event_handle_any_event (in
/usr/local/lib/libecore_x.so.1.16.1)" at the other end of the chain. I
can provide the massif output file (about 240k) if anyone would like
to take a look.

Thanks,
-Conrad.

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

[e-users] tracking down memory issue

[Conrad Knight]

Hi,

I posted before about build problems with E19, and seem to have solved
those. For the record (and anyone searching the mailing list
archives)...
 - edje segfaults during elementary build was caused by left over
modules in /usr/local/lib/edje/. Have to run "make uninstall" in
_both_ efl and elementary source directories before building. Although
edje is installed with efl, some of its modules are installed by
elementary. These are apparently not compatible when a newer efl's
edje tries to load them.
 - constant crashing and respawning of efreetd was caused by loading
contents of a cache directory. As this was presumably first created by
E18, format change or corrupted contents were likely to blame. Nuking
the cache directory (~/.cache/efreet, i think it was) fixed this.

Anyway, with these problems solved, I decided to have a go at
enlightenment 0.20.2, with efl/elementary 1.16.1. It all works, but
i'm left with what appears to be an intermittent memory leak.

Currently I have the following status for enlightenment, having just
restarted it:

~$ ps u -p 3303
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
conrad3303  5.9  1.4 790196 119480 ?   Rl   11:39   1:45
/usr/local/bin/enlightenment

Leaving this running ovenight, with pretty much just chrome and
xscreensaver running, that %MEM value went up to just over 50% some 12
hours later. Issuing "enlightenment_remote -restart" brought that
right back down to 1.2%. Then, barely some 3 hours later with more
heavy use (opening/closing windows, etc.) it was up over 80%. So much
so, that the enlightenment desktop was unresponsive except for showing
cursor movement. I had to switch to a text terminal to kill
enlightenment.

I tracked down the efreetd crashing problem by running it under gdb
and using a backtrace. I'm afraid i have no idea how to go about
finding what's causing this memory usage, though. Any suggestions for
debugging welcome! :)

Thanks,
-Conrad.

-- 
Whenever and  wherever you want.

--
___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Re: [e-users] tracking down memory issue

[Cedric BAIL]

Hello,

On Mon, Jan 4, 2016 at 9:35 AM, Conrad Knight  wrote:
> I posted before about build problems with E19, and seem to have solved
> those. For the record (and anyone searching the mailing list
> archives)...
>  - edje segfaults during elementary build was caused by left over
> modules in /usr/local/lib/edje/. Have to run "make uninstall" in
> _both_ efl and elementary source directories before building. Although
> edje is installed with efl, some of its modules are installed by
> elementary. These are apparently not compatible when a newer efl's
> edje tries to load them.
>  - constant crashing and respawning of efreetd was caused by loading
> contents of a cache directory. As this was presumably first created by
> E18, format change or corrupted contents were likely to blame. Nuking
> the cache directory (~/.cache/efreet, i think it was) fixed this.
>
> Anyway, with these problems solved, I decided to have a go at
> enlightenment 0.20.2, with efl/elementary 1.16.1. It all works, but
> i'm left with what appears to be an intermittent memory leak.
>
> Currently I have the following status for enlightenment, having just
> restarted it:
>
> ~$ ps u -p 3303
> USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
> conrad3303  5.9  1.4 790196 119480 ?   Rl   11:39   1:45
> /usr/local/bin/enlightenment
>
> Leaving this running ovenight, with pretty much just chrome and
> xscreensaver running, that %MEM value went up to just over 50% some 12
> hours later. Issuing "enlightenment_remote -restart" brought that
> right back down to 1.2%. Then, barely some 3 hours later with more
> heavy use (opening/closing windows, etc.) it was up over 80%. So much
> so, that the enlightenment desktop was unresponsive except for showing
> cursor movement. I had to switch to a text terminal to kill
> enlightenment.
>
> I tracked down the efreetd crashing problem by running it under gdb
> and using a backtrace. I'm afraid i have no idea how to go about
> finding what's causing this memory usage, though. Any suggestions for
> debugging welcome! :)

Thanks for tracking the other issue and I will look if I can make edje
module more robust accross version change. As for tracking memory leak
the right tool this day is valgrind. It is going to slow down the
tracked software quite a lot ! Ideally you want to run enlightenment
in Xephyr so that you don't impact your main use, but that means you
won't see leak coming from the OpenGL backend. You can do the
following :
Xephyr :1.0 &
enlightenment_start -massif -display :1.0

Once you quick enlightenment, there will be a file of form massif.$PID
in the directory where you launched enlightenment from. You can open
that file using massif-visualizer and look at what is constantly
increasing.
-- 
Cedric BAIL

--
___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users