gdImageDestroy() segfault

[programmador]

gdImageDestroy() segfaults randomly when the program makes anything long after creating an image
It stops segfaulting when I comment out //FreeImage(v); line in finalize() function in nGDImage.c.
So it looks like garbage collector tries to free an image which hasn't been created to that moment or smth like that...

[programmador]

Oh no, it starts again if the load is alittle higher.

Test1.hx:51: 199_0.05658846667+14.25486887 = 14.25486887
Test1.hx:51: 199_0.05658846667+14.25486887 = 14.25486887
Test1.hx:51: 199_0.05658846667+14.25486887 = 14.25486887
Test1.hx:51: 199_0.05658846667+14.25486887 = 14.25486887
Test1.hx:51: 199_0.05658846667+14.25486887 = 14.25486887
Test1.hx:51: 199_0.05658846667+14.25486887 = 14.25486887
libpng warning: Image height exceeds user limit in IHDR
gd-png: fatal libpng error: Invalid IHDR data
gd-png error: setjmp returns error condition
*** glibc detected *** neko: double free or corruption (!prev): 0x00000000017f6650 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x75b46)[0x7f70cd016b46]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x6c)[0x7f70cd01b87c]
/usr/lib/x86_64-linux-gnu/libgd.so.2(+0x130b7)[0x7f70cbe3b0b7]
/usr/lib/x86_64-linux-gnu/libgd.so.2(gdDPExtractData+0x9b)[0x7f70cbe3b47b]
/usr/lib/x86_64-linux-gnu/libgd.so.2(gdImagePngPtr+0x43)[0x7f70cbe404c3]
/usr/lib/neko/nGD.ndll(ImagePngData+0x19)[0x7f70cc074489]
/usr/lib/libneko.so.0(neko_interp_loop+0x3244)[0x7f70cd334e74]
/usr/lib/libneko.so.0(neko_interp+0x1d0)[0x7f70cd335da0]
/usr/lib/libneko.so.0(neko_vm_execute+0x6d)[0x7f70cd335ead]
/usr/lib/libneko.so.0(+0xe2d0)[0x7f70cd3362d0]
/usr/lib/libneko.so.0(neko_val_callEx+0x391)[0x7f70cd3310f1]
neko[0x4014db]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)[0x7f70ccfbfead]
neko[0x401769]
======= Memory map: ========
00400000-00403000 r-xp 00000000 08:01 407041 /usr/bin/neko
00602000-00603000 rw-p 00002000 08:01 407041 /usr/bin/nekoАварийный останов

[TheHippo]

If you comment out the FreeImage(v) call how the does memory usage behave?

[programmador]

I tried to use valgrind but there were some troubles.
If I measure all the memory which program uses with all syscalls and other stuff (----pages-as-heap=yes) it shows the same result - about 19MB.
If I measure without this option it prints just zero - looks like a program doesn't use memory :-).
If I measure with stacks - it prints some data but also with no difference between having FreeImage(v); commented or not.
The most interesting that valgrind executes the program very slowly and it 100% segfaults. If I execute the program without a profiler - it runs faster and does not segfault.