Possible heap corruption with 2.75?
Posted: Sun Jun 14, 2009 7:15 pm
Hi,
I recently upgraded to 2.75. With beta1, rc3 and the current version in the repository (r1695), I have had errors with the heap getting corrupted on machines running both Windows and Linux. With 2.73 and 2.74, I haven't had any errors and the code is very stable.
Does anyone know of something that I might have to change in how my code is calling bullet that is different in 2.75 than its predecessors? E.g. Are initialization and clean up still the same? (When I run the demo applications, I don't run into any memory issues.)
I have used valgrind and a Windows memory checker and haven't picked up any leaks in my code. To make matters worse, the place where the debuggers pick up the corruption appears to be pretty random, depending on the scenario the code is passed (e.g. sometimes it occurs deep within bullet code; other times in the rendering or control loop, etc.).
Has anyone else had similar problems?
Thanks.
I recently upgraded to 2.75. With beta1, rc3 and the current version in the repository (r1695), I have had errors with the heap getting corrupted on machines running both Windows and Linux. With 2.73 and 2.74, I haven't had any errors and the code is very stable.
Does anyone know of something that I might have to change in how my code is calling bullet that is different in 2.75 than its predecessors? E.g. Are initialization and clean up still the same? (When I run the demo applications, I don't run into any memory issues.)
I have used valgrind and a Windows memory checker and haven't picked up any leaks in my code. To make matters worse, the place where the debuggers pick up the corruption appears to be pretty random, depending on the scenario the code is passed (e.g. sometimes it occurs deep within bullet code; other times in the rendering or control loop, etc.).
Has anyone else had similar problems?
Thanks.