More comments;
Next test; valgrind runs fine if I add
"--show-reachable=no --show-possibly-lost=no"
Best
/pto
On Sun, 22
Jan 2012 12:42:25 +0100, Peter Toft wrote:
> Thanx Philippe
>
> I
re-ran valgrind 3.6.0 with "-v -v --stats=yes --profile-heap=yes" and
just before the memory crash I do see new output, but I cannot
understand what I should see from this.
>
> --19677-- client : 23 sbs,
573568 bs, 3297/3297 free bs, 100470784 mmap, 53280112 loan--------
Arena "client": 100470784 mmap'd, 53280112/53280112 max/curr --------
53,280,112 in 570,271: replacemalloc.cm.1
> --19677-- tool : 15 sbs,
745570 bs, 7/7 free bs, 62914560 mmap, 26228624 loan-------- Arena
"tool": 62914560 mmap'd, 26228624/26228624 max/curr -------- 128 in 2:
hashtable.Hc.1 128 in 2: commandline.sua.2 128 in 2: commandline.sua.3
256 in 1: initimg-linux.sce.5 528 in 2: mc.cSVT.1 (sec VBit table) 704
in 30: mc.resi.1 1,264 in 7: errormgr.mre.2 6,160 in 1: hashtable.Hc.2
8,368 in 166: mc.iaLL.1 2,359,456 in 2: hashtable.resize.1 23,851,504 in
745,348: mc.cMC.1 (a MC_Chunk)
> --19677-- client : 29 sbs, 733108 bs,
9946/9946 free bs, 131190784 mmap, 68070720 loan-------- Arena "client":
131190784 mmap'd, 68070720/68070720 max/curr -------- 68,070,720 in
723,162: replacemalloc.cm.1
> --19677-- client : 30 sbs, 678741 bs,
7692/7692 free bs, 135385088 mmap, 76847008 loan-------- Arena "client":
135385088 mmap'd, 76847008/76847008 max/curr -------- 76,847,008 in
671,049: replacemalloc.cm.1
> --19677-- client : 33 sbs, 679112 bs,
7710/7710 free bs, 176037888 mmap, 115553744 loan-------- Arena
"client": 176037888 mmap'd, 115553744/115553744 max/curr --------
115,553,744 in 671,402: replacemalloc.cm.1
> --19677-- TT/TC: initialise
sector 1--19677-- client : 35 sbs, 679573 bs, 7752/7752 free bs,
186687488 mmap, 128247232 loan-------- Arena "client": 186687488 mmap'd,
128247232/128247232 max/curr -------- 128,247,232 in 671,821:
replacemalloc.cm.1
> --19677-- REDIR: 0x31706796f0 (strcspn) redirected
to 0x4908e00 (strcspn)--19677-- client : 38 sbs, 627674 bs, 18400/18400
free bs, 201531392 mmap, 141531824 loan-------- Arena "client":
201531392 mmap'd, 141531824/141531824 max/curr -------- 141,531,824 in
609,274: replacemalloc.cm.1
> --19677-- client : 39 sbs, 626844 bs,
18316/18316 free bs, 216150016 mmap, 157200624 loan-------- Arena
"client": 216150016 mmap'd, 157200624/157200624 max/curr --------
157,200,624 in 608,528: replacemalloc.cm.1
> --19677-- client : 43 sbs,
621501 bs, 17684/17684 free bs, 232927232 mmap, 173009392 loan--------
Arena "client": 232927232 mmap'd, 173009392/173009392 max/curr --------
173,009,392 in 603,817: replacemalloc.cm.1
> --19677-- client : 47 sbs,
610298 bs, 23535/23535 free bs, 250429440 mmap, 190310464 loan--------
Arena "client": 250429440 mmap'd, 190310464/190310464 max/curr --------
190,310,464 in 586,763: replacemalloc.cm.1
> --19677-- client : 50 sbs,
587330 bs, 34531/34531 free bs, 495476736 mmap, 437869472 loan--------
Arena "client": 495476736 mmap'd, 437869472/437869472 max/curr --------
437,869,472 in 552,799: replacemalloc.cm.1
> --19677-- client : 51 sbs,
587332 bs, 34531/34531 free bs, 613445632 mmap, 555834320 loan--------
Arena "client": 613445632 mmap'd, 555834320/555834320 max/curr --------
555,834,320 in 552,801: replacemalloc.cm.1
> --19677-- TT/TC: initialise
sector 2--19677-- client : 63 sbs, 591866 bs, 69362/69362 free bs,
676491264 mmap, 611707216 loan-------- Arena "client": 676491264 mmap'd,
611707216/611707216 max/curr -------- 611,707,216 in 522,504:
replacemalloc.cm.1
>
> Clues?
>
> Best
>
> Peter
>
> On Fri, 20
Jan 2012 17:30:38 +0100, WAROQUIERS Philippe wrote:
>
>> 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:p...@linuxbog.dk]
>>> 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
>
> --
> Peter Toft, PhD
>
http://petertoft.dk
--
Peter Toft, PhD
http://petertoft.dk
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
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-dev2
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
