Issue 50237 - MLK: Basic objects after some open/close
Summary: MLK: Basic objects after some open/close
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: 680m106
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: ab
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-02 13:33 UTC by malte_timmermann
Modified: 2013-08-07 14:41 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description malte_timmermann 2005-06-02 13:33:14 UTC 
Start a office with an empty text document.
Run a macro which creates and closes a lot of empty text documents.
Seems some basic objects are leaking...
Comment 1 ab 2005-06-02 17:16:33 UTC 
ab->mt: It only seems so... :-)

I debugged a corresponding macro and found that for every variable
- including variables in other libraries, e.g. the wizards - declared 
as public SbxObject::Make() is called when the macro is executed.
The SbxProperty instances created there are not deleted afterwards.
But this is no leak as these instances are deleted the next time the
macro is started. The new instances replace the old ones and force
the old ones to be deleted. I checked this using the debugger. This is 
also true for the SbxVarEntry instances created in SbxArray::GetRef
shown by your memory log. 

So this is not really a leak. There's always only one set of allocated
objects and the memory usage does not increase every time the macro 
runs. All allocated objects are freed but not in the time frame of your
test. The last set of objects will be deleted together with the Basic
object itself.

-> INVALID
Comment 2 Joost Andrae 2005-06-30 14:49:10 UTC 
.
Comment 3 malte_timmermann 2005-06-30 16:10:17 UTC 
Verified...
Comment 4 Mathias_Bauer 2005-11-18 08:13:24 UTC 
closing