Repeated Freezing, Then Crashing

[pluby]

I think that I have fixed the memory leak. I found that the memory leak was caused by NeoOffice's underlying OpenOffice.org code that handles the key shortcuts in menus.

I fixed this bug by using the same approach that the OpenOffice.org engineers used to fix OpenOffice.org bug 120029.

Can you install either of the following test patches and tell us if you still see memory use climb rapidly when you switch into and out of editing an embedded object? To see memory use, launch the /Applications/Utilities/Activity Monitor and watch the "Real Memory" column for NeoOffice. Memory use should climb about 10 MB for each of the first few switches but then then rate of climb should drop to less than 1 MB after that:

NeoOffice 3.3:
http://juliette.neooffice.org/test/NeoOffice-3.3-Patch-9-Test-5-Intel.dmg

NeoOffice 2013:
http://juliette.neooffice.org/test/NeoOffice-2013-Test-6-Intel.dmg

Patrick

[gbh]

Testing now. Will let you know. Thanks.

[pluby]

FYI. I found another small memory leak in our code. Whenever a window's mouse cursor changed, our code would retain that window and never release it. As a result, the memory attached to such windows would never get released even after such windows were closed.

I have fixed this second memory leak in the following test patch:

NeoOffice 3.3:
http://juliette.neooffice.org/test/NeoOffice-3.3-Patch-9-Test-6-Intel.dmg

NeoOffice 2013:
http://juliette.neooffice.org/test/NeoOffice-2013-Test-7-Intel.dmg

Patrick

[pluby]

FYI. I have included the fix for the two memory leaks in NeoOffice 3.3 Patch 10. The patch can be downloaded from the NeoOffice patch download page.

Patrick