Ticket #722 (closed: fixed)
Fix memory leaks in Geometry
Reported by: | Russell Taylor | Owned by: | Russell Taylor |
---|---|---|---|
Priority: | major | Milestone: | Iteration 19 |
Component: | Keywords: | ||
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description
Valgrind flags up quite a significant number...
Attachments
Change History
Changed 11 years ago by Russell Taylor
- Attachment remaining-issues.txt added
Remaining memory issues as of 31st July
comment:5 Changed 11 years ago by Russell Taylor
The remaining issue is mainly around whether OpenCascade, through its internal memory manager, is holding onto a load of memory unnecessarily after its done its work. There's also something going on in ShapeFactory.
comment:8 Changed 11 years ago by Russell Taylor
- Status changed from assigned to closed
- Resolution set to fixed
That's all the geometry memory leaks that are highlighted by running the tests, apart from the OpenCASCADE ones (see attached document). A couple of points about these:
- They may be spurious. OpenCASCADE has its own memory management (based on a pool-type implementation) that may not play nicely with valgrind.
- OpenCASCADE is only used if you don't already have a cached geometry (vtp) file - i.e. rarely.
Note: See
TracTickets for help on using
tickets.