0021907: Memory leak in OCAF document

ID	Project	Category	View Status	Date Submitted	Last Update

0021907	Open CASCADE	OCCT:Application Framework	public	2010-07-16 16:10	2013-10-03 11:25

Reporter	vro	Assigned To	vro
Priority	normal	Severity	feature
Status	closed	Resolution	no change required
OS	All

Summary	0021907: Memory leak in OCAF document
Description	From 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.
Tags	No tags attached.

Test case number

2010-07-16 16:15	vro-occ21907-v1.zip (4,114 bytes)

2010-07-16 16:50	vro-occ21907-v2.zip (3,987 bytes)

2010-07-20 16:24	vro-occ21907-v3.zip (4,000 bytes)

2010-07-20 16:44	vro-occ21907-v4.zip (3,994 bytes)

vro 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.

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 =>