Still having that apparent GC problem (with Tango on my machine), does anyone
have (some GC test code) that they
can recommend that I run so that I can confirm that my GC is / is not working?
when I run without valgrind of course, it runs faster so I don't need 4 minutes
...
in less than 1 minute, it went from ~ 64 Mbytes to ~ 400 Mbytes
--- trying with GC.collect() and GC.minimize() in main loop ... : Same result.
hmm..
Are you sure that I'm not somehow linking wrong and not getting a functioning
GC ?
+ After running for 4 minutes with valgrind:
==3214== 224,418,252 bytes in 486,492 blocks are definitely lost in loss record
1,030 of 1,030
==3214==at 0x4024918: malloc (in
/usr/lib/valgrind/vgpreload_memc
> I think that the GC doesn't give back memory to the system. It keeps it
> for future use.
Ah, but I'm seeing the memory usage increasing over time still...
for a test run of some sort, my largest loss record is:
==3191== 16,240,909 bytes in 35,757 blocks are definitely lost in loss record
1,
Hi, I have (sort of) 2 questions:
Background:
I was doing some coding using Phobos, and recently switched to using Tango.
1. I'm trying to build using dsss and it says :
/usr/bin/ld: cannot find -lphobos
collect2: ld returned 1 exit status
--- errorlevel 1
Command /usr/bin/rebuild returned with c
