[Bf-cycles] Cycles memory leaks
sergey.vfx at gmail.com
Tue Jul 12 20:12:50 CEST 2016
In Blender we do use guarded allocator everywhere, including Cycles (at
least for it's major parts). I did not see any leaks reported. So can you
elaborate a bit more which exact memory is leaking?
Think it worth addressing the issue unless it leads to some nasty code
workaorunds or makes integration into other software creepier.
But all that being said, please make sure you're doing similar thing to
what we do in blender_python.cpp:exit_func(). This was the trick to make
staticly initialized data to be freed and make Blender's integration happy.
We should probably need to move that code to ccl::Session::exit() and call
from standalone app as well.
On Tue, Jul 12, 2016 at 6:31 PM, Thomas Krebs <Thomas.Krebs at mecadtron.de>
> We are currently trying to integrate cycles into our 3d app.
> We have successfully implemented a collada exporter from our app
> and produced some nice images in Blender.
> Now we got the standalone cycles app compiled and running.
> We found that cycles leaks quite some bit from some static
> initializers. As we try to solve leaks by monitoring leaks reports from
> MSVC this is somewhat problematic.
> Personally I would prefer not to have static initializers rather than
> some initialize/terminate functions, which would make cycles even more
> usable for integration in other systems.
> Is there some effort going on to address that situation or would such
> an effort be welcome?
> We might supply changes for that but we would leave it up to more
> experienced submitters to integrate such changes, if at all.
> Bf-cycles mailing list
> Bf-cycles at blender.org
With best regards, Sergey Sharybin
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Bf-cycles