@Stephan,
Thanks for the suggestion... we changed out code to run the script
instead of the binary directly.
Also, this hasn't changed our issue (as was probably expected)... even
after we take down / stop the PPT file, top still reports massive memory
usage for the soffice process.
-Chri
On 11/03/10 13:47, Chris Rider wrote:
We are starting the document server like this:
/opt/openoffice.org3/program/soffice.bin
"-accept=socket,host=localhost,port=2083;urp;StarOffice.ServiceManager"
-nolockcheck -nologo -impress -norestore -invisible &
Somewhat unrelated, please note that runnin
@Cor,
Thanks for following up for more details...
We tried using 3.3 this morning and it didn't really work with our
DocumentLoader program and seemed a bit buggy-ish ~~ so maybe a no-go
there (at least until 3.3. is official).
Yeah, you're right... the shakeup is a whole different subject..
Mathias,
You're correct in all your statements.
We are starting the document server like this:
/opt/openoffice.org3/program/soffice.bin
"-accept=socket,host=localhost,port=2083;urp;StarOffice.ServiceManager"
-nolockcheck -nologo -impress -norestore -invisible &
Our DocumentLoader then is t
Morgen Mathias,
Nur falls es dich interessiert:
Deine Mail kommt bei mir als von gestern 18:43 an...
Thomas
On 02.11.2010 18:43, Mathias Bauer wrote:
> Hi Chris,
>
> On 02.11.2010 13:40, Chris Rider wrote:
>> I hope this is an active mailing list ~ we have a serious issue with the
>> documen
Hi Chris,
On 02.11.2010 13:40, Chris Rider wrote:
I hope this is an active mailing list ~ we have a serious issue with the
document server and are trying to track down some more knowledge that
might exist about it.
I have new information from further testing, but here's a quick summary:
We have
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).
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 memor
and then trie to uses Cor's idea, open and closing 2 OO-services
On 2/11/2010 17:39, Fernand Vanrie wrote:
Chris ,
gives 3.3 a trie ?
FYI, we are using 3.2.1
Chris
On 11/02/2010 12:02 PM, Fernand Vanrie wrote:
Chris ,
Thanks for the comment/insight... I'll try to investigate, but not
FYI, we are using 3.2.1
Chris
On 11/02/2010 12:02 PM, Fernand Vanrie wrote:
Chris ,
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 tak
Chris ,
gives 3.3 a trie ?
FYI, we are using 3.2.1
Chris
On 11/02/2010 12:02 PM, Fernand Vanrie wrote:
Chris ,
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/re
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
Chris ,
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
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,
Chris ,
I have no experience with server applications but in the past, i found
some "leaks" when using "ImageControls", its not necerarly the document
itselfs who leaks, Trye to reproduce the operation on a local machine ad
see when or where the memory eating starts ?
Fernand
I hope this is
I hope this is an active mailing list ~ we have a serious issue with
the document server and are trying to track down some more knowledge
that might exist about it.
I have new information from further testing, but here's a quick summary:
We have a program that calls the document server to load
16 matches
Mail list logo
