* Patrick Shanahan <[email protected]> [06-30-13 21:18]: > * Patrick Shanahan <[email protected]> [06-30-13 16:43]: > > * johannes hanika <[email protected]> [06-30-13 15:38]: > > > 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? > > > > No, prior instance. Closed it after noticing the memory claimed by > > darktable. First time I noticed it using more than firefox. > > > > > a valgrind run with --leak-check=full would be a start. > > > > I can do that. jfyi, I reverted to 1.1.3-1.5.3 and the increase in memory > > usage since darktable start in minimal. > > > > How do I tell valgrind to make a report I can provide? > > ==30520== LEAK SUMMARY: > ==30520== definitely lost: 49,655,629 bytes in 35,241 blocks > ==30520== indirectly lost: 4,043,876 bytes in 7,307 blocks > ==30520== possibly lost: 812,872,618 bytes in 30,398 blocks > ==30520== still reachable: 5,216,615 bytes in 28,404 blocks > ==30520== suppressed: 0 bytes in 0 blocks > ==30520== Reachable blocks (those to which a pointer was found) are not shown. > ==30520== To see them, rerun with: --leak-check=full --show-reachable=yes > ==30520== > ==30520== For counts of detected and suppressed errors, rerun with: -v > ==30520== Use --track-origins=yes to see where uninitialised values come from > ==30520== ERROR SUMMARY: 10004664 errors from 4729 contexts (suppressed: 4 > from 3) > > is this sufficient?
Another test failed with: ==30792== More than 10000000 total errors detected. I'm not reporting any more. ==30792== Final error counts will be inaccurate. Go fix your program! ==30792== Rerun with --error-limit=no to disable this cutoff. Note ==30792== that errors may occur in your program without prior warning from ==30792== Valgrind, because errors are no longer being displayed. ==30792== full text: http://wahoo.no-ip.org/~pat/darktable.mem.txt -- (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
