Am Montag, 11. März 2013 um 13:42:34, schrieb Kornel Benko <kor...@lyx.org> > > Trying... takes nearly forever ... only 1 of my 4 cpu's is busy (100%) ... > > will mail again, when (and if?) the seach under valgrind ends. > > > JMarc
So, search finished, no visible memory lost.
The dialog
Opened files: The end is reached... Do you want to proceed at start
is displayed.
Checking No
Dialog ends.
This is totally different to the behaviour without valgrind.
Ending the lyx session... takes long ... about 10 seconds. This is the valgrind
summary output
==11211== HEAP SUMMARY:
==11211== in use at exit: 1,830,248 bytes in 10,246 blocks
==11211== total heap usage: 122,625,228 allocs, 122,614,982 frees,
24,147,890,589 bytes allocated
==11211==
==11211== LEAK SUMMARY:
==11211== definitely lost: 33,700 bytes in 189 blocks
==11211== indirectly lost: 59,454 bytes in 1,606 blocks
==11211== possibly lost: 15,783 bytes in 59 blocks
==11211== still reachable: 1,721,311 bytes in 8,392 blocks
==11211== suppressed: 0 bytes in 0 blocks
==11211== Rerun with --leak-check=full to see details of leaked memory
==11211==
==11211== For counts of detected and suppressed errors, rerun with: -v
==11211== Use --track-origins=yes to see where uninitialised values come from
==11211== ERROR SUMMARY: 3612 errors from 37 contexts (suppressed: 2 from 2)
I see, I should rerun, oh well ... this may take a while ...
Kornel
signature.asc
Description: This is a digitally signed message part.
