To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112766
------- Additional comments from c...@openoffice.org Wed Jul 7 14:25:34 +0000 2010 ------- Using my own x86_64 3.2.1 build, which is effectively the same as vanilla, i.e. no magic leak patches added, just to test the most basic case, i.e... Launch soffice.bin -writer get its PID and top -p thatpid PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 17993 caolan 20 0 930m 82m 61m S 0.0 1.4 0:01.01 soffice.bin close writer window, back to start panel 17993 caolan 20 0 951m 88m 63m S 0.0 1.5 0:01.40 soffice.bin file->new->document 17993 caolan 20 0 951m 88m 63m S 14.6 1.5 0:01.85 soffice.bin close writer window, back to start panel 17993 caolan 20 0 952m 89m 63m S 1.7 1.5 0:02.17 soffice.bin file->new->document 17993 caolan 20 0 951m 88m 63m S 1.3 1.5 0:02.66 soffice.bin close writer window, back to start panel 17993 caolan 20 0 952m 89m 63m S 8.3 1.5 0:02.93 soffice.bin file->new->document 17993 caolan 20 0 951m 88m 63m S 14.3 1.5 0:03.43 soffice.bin so it looks like we're stable in memory use in that scenario. cmc->drichard: do you get basically the same with this test. i.e. iterating through "Launch a single blank writer window", close it back to the start panel, and reopening another single blank writer window." --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
