[Bf-python] Error Totblck

[models at paposo.com]

It is a memory leak. I believe that it means that not all of the datablocks
were freed when blender exited. In other words malloc() was called to
allocate data but free() was never called to clean it up. Mostly calls to
malloc() occur to make space for the X->data but can also be called for temp
data storage or subitems of other items. When callocN() is called the global
Totblock counter is incremented. When freeN() is called the global Totblock
counter is decremented. When exit() is called it tries to free all the data
allocated by malloc(). When done if the Totblock counter is not 0 you have a
memory leak and it prints out "Error Totblock...".  Some functions have
corresponding calls to make_xxx() and free_xxx(). If you call something like
make_editmesh() without a call to free_editmesh() later then data allocated
in make_editmesh() doesn't get cleaned up when exit() is called because it
was expecting to clean up certain datablocks only. I don't have the problem
though (at least not with normal releases) on windows.
exit_usiblender()
MEM_callocN()
MEM_freeN()

----- Original Message -----
From: "Jacques Guignot" <guignot at wanadoo.fr>
To: <bf-python at blender.org>
Sent: Friday, October 31, 2003 6:42 AM
Subject: Re: [Bf-python] Error Totblck


> Yes, this warning is present since ages...
> I have no idea where it comes from...
> Memory allocation problem, surely, but where?
> Rather find a needle in a haystack  ;-(
>
>
> _______________________________________________
> Bf-python mailing list
> Bf-python at blender.org
> http://www.blender.org/mailman/listinfo/bf-python
>
>