Archived issue #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.
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.
Public activity
1 archived note
Participants are labeled by their role within this record.
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.
Related records