Hi Chris, Chris Rider wrote (02-11-10 19:10)
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!
Thanks, Obviously, I'll check my contact to see if I can provide more details. Looking at your comment above, I have the idea that it may have more in it, than I was able to explain right now.
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?
Yip.
I've heard rumors of a shakeup at Oracle / OpenOffice.... I hope we the users aren't going to bear the brunt of it!
That's a totally different subject. And I fully agree with you of course! Best regards, Cor -- - giving openoffice.org its foundation :: The Document Foundation - --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
