Page 1 of 1
[Solved] Java program was stopped unexpectedly
Posted: Tue Oct 08, 2013 8:30 pm
by VV_RIP
Hi! I'm using OO API (Open Ofiice v3.2) to create reports (OO Writer). But ... when OpenOffice process took about 260 MB of RAM, it stopped and wasn't work! If I stop the process, It will start working. Then it works some time, and stop again! What is it? And why OpenOffice takes very many memory?
P.s. I'm sorry for mistakes, my knowlarge of English is bad
... I want to believe, that you can understand me
.
Re: Java program was stopped unexpectedly
Posted: Thu Oct 10, 2013 5:14 pm
by VV_RIP
Oh, I'm sorry, I mistake. My OO version is 3.4.1, if this will help.
Re: Java program was stopped unexpectedly
Posted: Thu Oct 10, 2013 5:34 pm
by RoryOF
Try increasing memory options in /Tools /Options/ OpenOffice.org : Memory, then restart OpenOffice to apply this change. It may help. I doubt it will do any harm.
Re: Java program was stopped unexpectedly
Posted: Thu Oct 10, 2013 6:37 pm
by VV_RIP
Yes! Thanks!
I installed OO 4.0.1. But ... unfortunately, it has limit 256MB of RAM
It takes 210-220MB in real, and after this, sometimes I can't open OO Writer, while OO process is working.
Also it has one setting which clear RAM with 1 minute interval, but it isn't work ... So, it's bad, I need kill process from time to time ...
Re: Java program was stopped unexpectedly
Posted: Thu Oct 10, 2013 6:48 pm
by RoryOF
The solution may be to compile a version of OpenOffice for yourself, which uses more RAM allocation. The code is available at
svn co https://svn.apache.org/repos/asf ... fice/trunk
with compile notes at
http://wiki.openoffice.org/wiki/Documen ... _Guide_AOO
As far as I know there is about 300MB of source code, so I've never looked into customisation or compiling.
Re: Java program was stopped unexpectedly
Posted: Fri Oct 11, 2013 2:56 pm
by VV_RIP
Oh ... It's bad solution for me ... I do open source library ...
Re: Java program was stopped unexpectedly
Posted: Sat Nov 02, 2013 7:27 pm
by VV_RIP
Omg ... I mistake! I forgot close documents after saving ...
I found this on one of topics:
Code: Select all
XCloseable xclosable =
(XCloseable)UnoRuntime.queryInterface(XCloseable.class, doc);
xclosable.close(true);
But i didn't see this nowhere. It's strange ... May be I need read documentation more and mindfully.