On Mon, Jul 1, 2013 at 7:28 AM, Patrick Shanahan <[email protected]> wrote:
> * johannes hanika <[email protected]> [06-30-13 15:04]:
> > the image cache is gradually allocated until the maximum load (depending
> on
> > your prefs) is reached. your data by itself is no indication of a memory
> > leak.
>
> Ok, I have not shown you something you need to see. I have been
> experimenting with darktable for quite some time, > 6 months, and have
> never seen memory consumption by darktable drive my 12gb
with the 2.6G usage in your numbers?
a valgrind run with --leak-check=full would be a start.
j.
> systen into swap
> space. What do you need to see to prove or disprove, providing I can
> deliver it?
>
> tks,
> --
> (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711
> http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2
> http://en.opensuse.org openSUSE Community Member
> Registered Linux User #207535 @ http://linuxcounter.net
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Darktable-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/darktable-users
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Darktable-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-users
