Kp 513e7c05e9 Remove force-free of "leaked" memory in mem_display_blocks ... mem_display_blocks runs before global destructors, so it reports as leaked any memory which is managed by a global scope object with a destructor. If mem_display_blocks calls mem_free, and the destructor later calls mem_free, a double-free results, and usually leads to a crash. Even if the memory were actually leaked, freeing it does not help because the program will exit soon anyway. Reported-by: zico <https://github.com/dxx-rebirth/dxx-rebirth/issues/85>		2015-06-12 02:54:53 +00:00
..
2d	Hoist store in gr_internal_string0_template	2015-05-09 17:39:02 +00:00
3d	Fix gcc-4.6 interpreter build	2015-05-22 03:33:19 +00:00
arch	Merge pull #39 into unification/master	2015-06-07 16:21:37 +00:00
editor	Simplify fix_sincos calls	2015-06-02 03:03:31 +00:00
main	Fix serial endian_access -fno-inline build	2015-06-11 03:06:58 +00:00
mem	Remove force-free of "leaked" memory in mem_display_blocks	2015-06-12 02:54:53 +00:00
misc	Raise PHYSFSX_exists bool check to caller	2015-05-09 17:39:02 +00:00