On 11/1/18 9:17 AM, Carsten Haitzler wrote:
On Wed, 31 Oct 2018 14:25:57 +0100 leoutat...@gmx.fr said:
On 10/31/18 1:00 PM, Carsten Haitzler wrote:
On Thu, 27 Sep 2018 23:28:56 +0200 leoutat...@gmx.fr said:
On 9/26/18 7:49 PM, Carsten Haitzler wrote:
hmmm... that leak isn't in normal
On 11/1/18 9:17 AM, Carsten Haitzler wrote:
On Wed, 31 Oct 2018 14:25:57 +0100 leoutat...@gmx.fr said:
On 10/31/18 1:00 PM, Carsten Haitzler wrote:
On Thu, 27 Sep 2018 23:28:56 +0200 leoutat...@gmx.fr said:
On 9/26/18 7:49 PM, Carsten Haitzler wrote:
hmmm... that leak isn't in normal
On Wed, 31 Oct 2018 14:25:57 +0100 leoutat...@gmx.fr said:
> On 10/31/18 1:00 PM, Carsten Haitzler wrote:
> > On Thu, 27 Sep 2018 23:28:56 +0200 leoutat...@gmx.fr said:
> >
> >> On 9/26/18 7:49 PM, Carsten Haitzler wrote:
> >>
> >>>
> >>> hmmm... that leak isn't in normal malloc. paths. it seems
On 10/31/18 1:00 PM, Carsten Haitzler wrote:
On Thu, 27 Sep 2018 23:28:56 +0200 leoutat...@gmx.fr said:
On 9/26/18 7:49 PM, Carsten Haitzler wrote:
hmmm... that leak isn't in normal malloc. paths. it seems pretty ok -
climbs a bit over time. this smells like something to do with drm/gbm
On Thu, 27 Sep 2018 23:28:56 +0200 leoutat...@gmx.fr said:
> On 9/26/18 7:49 PM, Carsten Haitzler wrote:
>
> >
> > hmmm... that leak isn't in normal malloc. paths. it seems pretty ok -
> > climbs a bit over time. this smells like something to do with drm/gbm
> > buffers. something not being
On 9/26/18 7:49 PM, Carsten Haitzler wrote:
hmmm... that leak isn't in normal malloc. paths. it seems pretty ok - climbs a
bit over time. this smells like something to do with drm/gbm buffers. something
not being released?
New valgrind -massif file today, 13 hours running enlightenment.
On Wed, 26 Sep 2018 18:18:23 +0200 leoutat...@gmx.fr said:
> On 9/26/18 3:30 PM, Carsten Haitzler (The Rasterman) wrote:
> > On Wed, 26 Sep 2018 13:37:42 +0200 leoutat...@gmx.fr said:
> >
> >> On 9/26/18 12:04 PM, Carsten Haitzler (The Rasterman) wrote:
> >>
> > you definitely have a leak.
On 9/26/18 3:30 PM, Carsten Haitzler (The Rasterman) wrote:
On Wed, 26 Sep 2018 13:37:42 +0200 leoutat...@gmx.fr said:
On 9/26/18 12:04 PM, Carsten Haitzler (The Rasterman) wrote:
you definitely have a leak. you want massif. so -massif option. then use
massif-visualizer to look at the trace
On Wed, 26 Sep 2018 13:37:42 +0200 leoutat...@gmx.fr said:
> On 9/26/18 12:04 PM, Carsten Haitzler (The Rasterman) wrote:
>
> >>> you definitely have a leak. you want massif. so -massif option. then use
> >>> massif-visualizer to look at the trace and you'll see it probably going
> >>> "up and
On 9/26/18 12:04 PM, Carsten Haitzler (The Rasterman) wrote:
even then i'm not sure i can usefully open it on a different system. i
have never tried. thus massif-visualizer.
May be you'll need original massif file name :
massif.out.20204
___
On 9/26/18 12:04 PM, Carsten Haitzler (The Rasterman) wrote:
you definitely have a leak. you want massif. so -massif option. then use
massif-visualizer to look at the trace and you'll see it probably going "up
and to the right". select a time point near the right/big end and start
digging
On Wed, 26 Sep 2018 12:10:06 +0200 Vincent Torri said:
> On Wed, Sep 26, 2018 at 12:05 PM Carsten Haitzler
> wrote:
> >
> > On Tue, 25 Sep 2018 21:43:29 +0200 leoutat...@gmx.fr said:
> >
> > > On 9/25/18 9:37 AM, Carsten Haitzler (The Rasterman) wrote:
> > > > On Mon, 24 Sep 2018 14:31:24 +0200
On Wed, Sep 26, 2018 at 12:05 PM Carsten Haitzler wrote:
>
> On Tue, 25 Sep 2018 21:43:29 +0200 leoutat...@gmx.fr said:
>
> > On 9/25/18 9:37 AM, Carsten Haitzler (The Rasterman) wrote:
> > > On Mon, 24 Sep 2018 14:31:24 +0200 leoutat...@gmx.fr said:
> > >
> > >> On 9/24/18 7:41 AM, Simon Lees
On Tue, 25 Sep 2018 21:43:29 +0200 leoutat...@gmx.fr said:
> On 9/25/18 9:37 AM, Carsten Haitzler (The Rasterman) wrote:
> > On Mon, 24 Sep 2018 14:31:24 +0200 leoutat...@gmx.fr said:
> >
> >> On 9/24/18 7:41 AM, Simon Lees wrote:
> >>> For a bit more info, whats the memory usage after 10
On 9/25/18 9:37 AM, Carsten Haitzler (The Rasterman) wrote:
On Mon, 24 Sep 2018 14:31:24 +0200 leoutat...@gmx.fr said:
On 9/24/18 7:41 AM, Simon Lees wrote:
For a bit more info, whats the memory usage after 10 minutes and after
8-12 hrs, it is likely that as you run more programs e needs to
On Mon, 24 Sep 2018 14:31:24 +0200 leoutat...@gmx.fr said:
> On 9/24/18 7:41 AM, Simon Lees wrote:
> > For a bit more info, whats the memory usage after 10 minutes and after
> > 8-12 hrs, it is likely that as you run more programs e needs to use more
> > memory, so having a couple more data
On 9/24/18 7:41 AM, Simon Lees wrote:
For a bit more info, whats the memory usage after 10 minutes and after
8-12 hrs, it is likely that as you run more programs e needs to use more
memory, so having a couple more data points would be useful.
I only run firefox, thunderbird, terminology and
On 20/09/2018 22:02, leoutat...@gmx.fr wrote:
> Hi
> When starting *wayland* session, enlightenment eats about 130M.
> After 4 hours running, e eats huge memory:
> htop
> enlightenment resident memory 3222M
> After restarting e, it's ok, about 100M
> Is it normal or is it a bug?
> system:
>
18 matches
Mail list logo
