We came up with a process that regularly restarts it before the memory
usage becomes too high, but this is not 100% desirable in our particular
application. We can't have any kind of interruption in how we display
content (brief flashes or anything). Also, it's challenging to monitor
the memory usage of this one particular process, programatically in our
application. Also, these aren't exactly "thin" clients, but they are
running a tight margin with resources, as we use them for quite
intensive media (1080p) among other things ~ so it's really not the best
solution to have to constantly monitor and check things in this manner,
or run redundant processes.... though you did provide a smart workaround
there, Cor, and we appreciate the suggestion!
If the document server has some issue with leaking memory, it should at
least be addressed in principle IMHO. Memory leaks are pretty serious
bugs, aren't they?
I've heard rumors of a shakeup at Oracle / OpenOffice.... I hope we the
users aren't going to bear the brunt of it!
Chris
On 11/02/2010 12:11 PM, Cor Nouws wrote:
Hi Chris,
Chris Rider wrote (02-11-10 16:47)
Thanks for the comment/insight... I'll try to investigate, but not
hopeful.
It happens once a document is closed, seemingly (could be on open,
too)... and each subsequent/repeated opening of the file takes longer
and longer. It really just seems like the memory isn't being cleared on
close, is my best guess.
I remember that someone told me setting up a service with OpenOffice.org:
He had two instances running, constantly checking the (memory) state
of the first.
When that got to bad, using the second and restarting the first.
Of course this all automatically. And it worked without probs.
Regards,
Cor
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org
For additional commands, e-mail: dev-h...@api.openoffice.org
