3 Commits

Include renames

Author	SHA1	Message	Date
asarium	e0395ab51a	Remove memory tracking code	2016-09-08 12:22:35 +02:00
asarium	5ba393ce5d	Fix for #768 ... Apparently MSVC 2013 allocates memory when locking a mutex which calls our allocation hook when the tries to call our memory tracking function which leads to a deadlock. Since there is no way of providing a memory allocation function for std::mutex the best solution is to simply disable the lock_guard for everything before MSVC 2015. That will probably corrupt the memory tracking values at some point but it's better than not being able to run FSO at all.	2016-08-07 23:45:38 +02:00
asarium	7b352e511c	Add new memory tracking subsystem ... This expands the existing system which only worked on Windows to all supported platforms. If the MSVC debug runtime is not present then its behavior is emulated by adding a header to each allocated memory block.	2016-07-29 11:02:45 +02:00