Élie Roux wrote:
>
valgrind -v --leak-check=full texlua luaotfload-tool.lua 2
results in the output here:
http://justpaste.it/2lq6
Well, it's not that bad, there is a memory leak of about 5Mb. It's a
lot, but far from 3Gb! but the database was not rebuilt entirely (I
guess). What about
valgrind -v --leak-check=full texlua luaotfload-tool.lua --update --force
?
Did this, and let it run for 7 hours. It did not finish. CPU was 100%
busy, but memory was not full. After stopping the program (ctrl+c), I got:
==30667== LEAK SUMMARY:
==30667== definitely lost: 2,958,863 bytes in 28,218 blocks
==30667== indirectly lost: 58,307,328 bytes in 59,833 blocks
==30667== possibly lost: 13,388,168 bytes in 24 blocks
==30667== still reachable: 100,485,349 bytes in 1,510,432 blocks
==30667== suppressed: 0 bytes in 0 blocks
==30667== Reachable blocks (those to which a pointer was found) are not
shown.
==30667== To see them, rerun with: --leak-check=full --show-reachable=yes
==30667==
==30667== ERROR SUMMARY: 88 errors from 88 contexts (suppressed: 2 from 2)
--30667--
--30667-- used_suppression: 2 dl-hack3-cond-1
==30667==
==30667== ERROR SUMMARY: 88 errors from 88 contexts (suppressed: 2 from 2)
cheers
Arno
