Quantcast

Significant Memory Leaks As An UNO Service Provider

classic Classic list List threaded Threaded
5 messages Options
Adam Tauno Williams Adam Tauno Williams
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Significant Memory Leaks As An UNO Service Provider

We run OOo/LOo headless in order to utilize services via UNO from a web
application.  Works great.  But it leaks memory rather badly,  and
eventually gets killed off for out-of-memory conditions.

Out of memory: Kill process 9145 (soffice.bin) score 475 or sacrifice
child
Killed process 9145, UID 0, (soffice.bin) total-vm:2792252kB,
anon-rss:666676kB, file-rss:76kB

Is there any means to invoke garbage collection when running headless
(as a service) to avoid these service outages?

--
For unsubscribe instructions e-mail to: [hidden email]
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Tom Tom
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Significant Memory Leaks As An UNO Service Provider

Hi :)
I think it's worth asking the devs, either iirc or perhaps a mailing list or just post a bug-report.  I think they might take memory leaks fairly seriously but i can't remember if it's really a serious issue. 
http://wiki.documentfoundation.org/BugReport
https://www.libreoffice.org/get-help/bug/
Regards from
Tom :)


--- On Tue, 24/4/12, Adam Tauno Williams <[hidden email]> wrote:

From: Adam Tauno Williams <[hidden email]>
Subject: [libreoffice-users] Significant Memory Leaks As An UNO Service Provider
To: [hidden email]
Date: Tuesday, 24 April, 2012, 19:10

We run OOo/LOo headless in order to utilize services via UNO from a web
application.  Works great.  But it leaks memory rather badly,  and
eventually gets killed off for out-of-memory conditions.

Out of memory: Kill process 9145 (soffice.bin) score 475 or sacrifice
child
Killed process 9145, UID 0, (soffice.bin) total-vm:2792252kB,
anon-rss:666676kB, file-rss:76kB

Is there any means to invoke garbage collection when running headless
(as a service) to avoid these service outages?

--
For unsubscribe instructions e-mail to: [hidden email]
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

--
For unsubscribe instructions e-mail to: [hidden email]
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Andreas Säger Andreas Säger
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Significant Memory Leaks As An UNO Service Provider

In reply to this post by Adam Tauno Williams
Am 24.04.2012 20:10, Adam Tauno Williams wrote:

> We run OOo/LOo headless in order to utilize services via UNO from a web
> application.  Works great.  But it leaks memory rather badly,  and
> eventually gets killed off for out-of-memory conditions.
>
> Out of memory: Kill process 9145 (soffice.bin) score 475 or sacrifice
> child
> Killed process 9145, UID 0, (soffice.bin) total-vm:2792252kB,
> anon-rss:666676kB, file-rss:76kB
>
> Is there any means to invoke garbage collection when running headless
> (as a service) to avoid these service outages?
>

https://issues.apache.org/ooo/show_bug.cgi?id=41675

I would have thought that this well known problem had been tackled in
LibreOffice.

JODConverter converts without memory leak:
http://sourceforge.net/projects/jodconverter/


--
For unsubscribe instructions e-mail to: [hidden email]
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Alex Thurgood Alex Thurgood
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Significant Memory Leaks As An UNO Service Provider

In reply to this post by Adam Tauno Williams
Le 24/04/12 20:10, Adam Tauno Williams a écrit :

Hi Adam,

> We run OOo/LOo headless in order to utilize services via UNO from a web
> application.  Works great.  But it leaks memory rather badly,  and
> eventually gets killed off for out-of-memory conditions.
>

Very, very old bug (as Andreas has pointed out) known from OOo times.
The only remedy I know of is to periodically dispose of the connection
before the app locks up, wait for the system to release the memory, and
restart it.

Alex


--
For unsubscribe instructions e-mail to: [hidden email]
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Cor Nouws Cor Nouws
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Significant Memory Leaks As An UNO Service Provider

In reply to this post by Adam Tauno Williams
Hi Adam,

Adam Tauno Williams wrote (24-04-12 20:10)

> We run OOo/LOo headless in order to utilize services via UNO from a web
> application.  Works great.  But it leaks memory rather badly,  and
> eventually gets killed off for out-of-memory conditions.
>
> Out of memory: Kill process 9145 (soffice.bin) score 475 or sacrifice
> child
> Killed process 9145, UID 0, (soffice.bin) total-vm:2792252kB,
> anon-rss:666676kB, file-rss:76kB
>
> Is there any means to invoke garbage collection when running headless
> (as a service) to avoid these service outages?

There isn't.
Usual solution for this is running few instances at the same time and
use a service to check the memory load, directing the task, and
killing/restarting a process when needed.
(People doing this with LibreOffice tell me that running as a server -
though not perfect - is considerably more stable than when they did so
with OpenOffice.org.)

Regards,

--
  - Cor
  - http://nl.libreoffice.org


--
For unsubscribe instructions e-mail to: [hidden email]
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Loading...