[Bf-committers] Blender linux console errors
hobbes1069 at gmail.com
Fri Mar 11 14:55:59 CET 2011
On Thu, Mar 10, 2011 at 10:48 PM, Campbell Barton <ideasman42 at gmail.com> wrote:
> I once spent some time trying to track down the allocations valgrind
> complains about and it seems they are either...
> * allocations by 3rd party libs - openal/python/x11 for eg, variables
> that are allocated once and kept
> * blenders own global C++ variables as mentioned before.
> * a handful of variables that are not freed on exit correctly like the
> event, happens with ReportList's sometimes.
> Each case could be fixed but it means adding extra init/free calls to
> the game engine for eg, or working out why the last event isn't freed,
> so its just a fair amount of time spent on tracking down something
> which isn't really causing anyone to run our of memory.
> To make valgrind play nice with python you need to build python
> for tracking down bugs which are unrelated to python just build
> without python is easiest.
> valgrind is really handy but I don't bother with its on exit memory
> leak messages, mostly our guarded-malloc gives more useful info.
> Theres a wiki page for more details
I recompiled with GUARDEDALLOC turned off and there is no more console
output including the GHOST error.
More information about the Bf-committers