> You have to provide more details. What's your method of testing whether > memory used by Dummy1 has been freed or not? RSS is at 110 MB here > during the loop in either case.
I looked at RSS as you did. > glibc does not and cannot immediately return every freed block back to > the system. Some blocks cannot be freed because they are just gaps > between heap-allocated regions and some blocks are intentionally not > freed to speed up following allocations. Damn! My background is embedded programming and I'm relatively new to Vala/GLib so I thought "g_free" is only an other name or a very thin wrapper for "free". I really think this is the solution. My appologize for unecessary stealing yours and others time :-( > You can normally trust valgrind's output to check whether your > application or library has memory leaks. I will do this for now on :-) -- Bernhard _______________________________________________ vala-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/vala-list
