There has been some improvements in the way some client malloc patterns
are
managed by Valgrind in 3.7.0. (see bug 250101).
In SVN 3.8.0, there has been a recent commit to further improve the
memory usage
(see bug 282230).
To have a better idea about what is happening, it would be good to
at least run with -v -v --stats=yes
and optionally with --profile-heap=yes (this somewhat increases the
memory usage).
This will very probably give some indications about what consumes that
memory.
You can then see the difference between a succesful run and a failing
run and/or
post the stats of the succesful/failing runs here.
Philippe
________________________________
From: Peter Toft [mailto:[email protected]]
Sent: Friday 20 January 2012 16:13
To: Valgrind users
Subject: [Valgrind-users] Extreme memory growth with Valgrind
3.6.0 and 3.7.0
Hi Valgrinders
I work from time to time with code which spans ~500.000 lines of
code.
When running I use 500-1000 MB on e.g. Red Hat Linux.
When prefixing my binary with valgrind I normally have good
sucess, but occationally (~1% of all cases) I see the memory growing
towards infinity.
Typically I set a general memory limit of 3 GB, where I kill the
binary . I reach that level ~1% of my runs.
For the remaining 99% of my valgrind tests I have a quite
limited memory overhead due to valgrind.
Have any of you seen similar behavior?
--
Peter Toft, PhD
http://petertoft.dk
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
