samlittlewood / carve

Automatically exported from code.google.com/p/carve
Other
0 stars 0 forks source link

Memory leak in carve::csg::CSG::compute #33

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Hi, I was looking into a blender memory leak and tracked it down to carve.

I used 2 ways to check the leak,
first by overriding the allocator in blender and counting the allocations, then 
breaking on the exact alloc which isnt freed.
- carve_unfree_alloc_blender.txt shows the backtrace of the alloc that is never 
freed.

To make sure it wasnt blender doing something strange or already fixed in HG, I 
grabbed latest source and ran valgrind with one of the tests that calls compute.
- carve_test_valgrind_report.txt also points to the same alloc as being unfreed.

hg info:
parent: 442:572b3510b2be tip

From reading:
carve/lib/intersect.cpp:1350... I couldnt figure out which class owns a_rtree 
and b_rtree. so even if you dont have time to fix the bug some hint here would 
be helpful.

Original issue reported on code.google.com by ideasma...@gmail.com on 27 Jun 2012 at 11:20

Attachments:

GoogleCodeExporter commented 9 years ago
I've fixed this, and a couple of other memory leaks, in the current branch 
heads.

Original comment by tobias.s...@gmail.com on 4 Jul 2012 at 3:33