To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=40658
User oc changed the following:
What|Old value |New value
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=40658
--- Additional comments from [EMAIL PROTECTED] Thu Feb 17 02:41:13 -0800
2005 ---
*** Issue 42916 has been marked as a duplicate of this issue. ***
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=40658
User mba changed the following:
What|Old value |New value
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=40658
--- Additional comments from [EMAIL PROTECTED] Wed Feb 16 11:58:25 -0800
2005 ---
The Windows Task Manager was used to discover this. I have found it to be a
very r
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=40658
--- Additional comments from [EMAIL PROTECTED] Wed Feb 16 09:52:31 -0800
2005 ---
My problem is that you don't report *how* you got data that shows memory leaks.
Man
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=40658
--- Additional comments from [EMAIL PROTECTED] Wed Feb 16 09:25:17 -0800
2005 ---
Confirmed/verified steadily increasing memory utilization using the script
provided
