To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=41675
------- Additional comments from mnas...@openoffice.org Thu May 21 23:14:24 +0000 2009 ------- I guess the problem with this sort of bug reports - and why they end up getting stuck in "OOo Later" forever - is that they are a bit too generic. We (as users) should follow the rule of "one problem, one issue". How can we expect the OOo team to fix all possible memory leaks for all possible import/export formats as part of a single issue? I tried to focus this issue on a specific case, i.e. PPT import which seemed to be the biggest culprit, in my comment (some 3 years ago now). But people keep adding generic complaints relating to various formats, with the only result that this issue will never be solved, because it's impossible to solve an ill-defined problem. (Incidentally, JODConverter 3.0 for its part now does provide a workaround: it automatically restarts OOo - see http://jodconverter.googlecode.com if interested.) --------------------------------------------------------------------- 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...@api.openoffice.org For additional commands, e-mail: issues-h...@api.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
