View Issue Details

IDProjectCategoryView StatusLast Update
0021907Open CASCADEOCCT:Application Frameworkpublic2013-10-03 11:25
Reportervro Assigned Tovro  
Status closedResolutionno change required 
Summary0021907: Memory leak in OCAF document
DescriptionFrom time to time a memory leak appears in an OCAF document. It happens either
in transient document or on storage / retrieval operation. In most cases a
custom data structure causes the leak and it takes much time for us to detect
and analyse a reason of the leak.
A new draw-command is aimed to help us to reveal a leak in an OCAF document as
well as keep OCAF memory leak free participating in non-regression tests.
TagsNo tags attached.
Test case number

Attached Files

  • (4,114 bytes)
  • (3,987 bytes)
  • (4,000 bytes)
  • (3,994 bytes)


related to 0024164 closedbugmaster Optimization of OCAF document closing 


2010-07-16 16:15 (4,114 bytes)

2010-07-16 16:50 (3,987 bytes)

2010-07-20 16:24 (4,000 bytes)

2010-07-20 16:44 (3,994 bytes)


2012-09-03 09:16

developer   ~0021381

This draw-command was good for detection of memory leaks in OCAF documents. But it was good a year ago. Since then, some logic of this draw-command was implemented inside OCAF (see the last modifications in the method TDocStd_Application::Close()). So, the draw-command is not useful now. I propose to close this issue.

Issue History

Date Modified Username Field Change
2010-07-20 15:56 bugmaster Assigned To bugmaster => vro
2010-07-20 15:56 bugmaster Status new => assigned
2011-08-02 10:32 bugmaster Category OCCT:OCAF => OCCT:Application Framework
2012-09-03 09:16 vro Note Added: 0021381
2012-09-03 09:16 vro Assigned To vro => bugmaster
2013-10-02 20:14 abv Relationship added related to 0024164
2013-10-02 20:14 abv Status assigned => feedback
2013-10-03 11:25 bugmaster Status feedback => closed
2013-10-03 11:25 bugmaster Assigned To bugmaster => vro
2013-10-03 11:25 bugmaster Resolution open => no change required
2013-10-03 11:25 bugmaster Fixed in Version EMPTY =>