On Mon, Jul 23, 2012 at 10:55 PM, Linyi Li <lilinyi921...@gmail.com> wrote: >> Exactly, it is the way it is working. And I believe this test only >> shows a part of leaks. It still needs other use cases to show >> different kinds of memory leaks. Perhaps checking existing memory leak >> bugs which has specific steps is a good direction. >> > > +1 > It is a good suggestion to test memory leak. Maybe we can write some test > cases based on memory leak defect. >
It is tricky. For example, a dialog box might have a memory leak when you click "cancel" but not when you click "OK" to exit it. The leak can depend on the exact steps taken by the user and the exact path through the code. We can never test all paths. Maybe one of the long-time OpenOffice developers know an answer to this: Have we ever considered having a custom memory allocator with a separate pool of memory for each loaded document? That way, when we close a document we can just free the entire block and avoid any memory leaks? We did this with SmartSuite years ago, and it was a big help. -Rob > -- > Best wishes. > Linyi Li
