I am running Suse 11.0 /w KDE 4.1, compiz & emerald. So far everything works great except OpenOffice Base as it locks up when I click any control.
So I ran it in a terminal to get feedback here is result.
bolo@linux-mg0v:~> GC Warning: Repeated allocation of very large block (appr. size 65536000):
May lead to memory leak and poor performance.
GC Warning: Repeated allocation of very large block (appr. size 524288000):
May lead to memory leak and poor performance.
GC Warning: Out of Memory! Returning NIL!
GC Warning: Out of Memory! Returning NIL!
Exception in thread "HSQLDB Timer @19af6037" java.lang.OutOfMemoryError
<<No stacktrace available>>
GC Warning: Repeated allocation of very large block (appr. size 524288000):
May lead to memory leak and poor performance.
GC Warning: Out of Memory! Returning NIL!
GC Warning: Out of Memory! Returning NIL!
GC Warning: Repeated allocation of very large block (appr. size 32768000):
May lead to memory leak and poor performance.
GC Warning: Out of Memory! Returning NIL!
GC Warning: Repeated allocation of very large block (appr. size 262144000):
May lead to memory leak and poor performance.
GC Warning: Out of Memory! Returning NIL!
GC Warning: Repeated allocation of very large block (appr. size 524288000):
May lead to memory leak and poor performance.
I have tried installing versions from Suse repo and Openoffice repo and both Java 5 & 6 to no avail.
I suspect a java problem but unsure, other Openoffice apps run fine.:mad:
Well besides running “oobase” in a terminal to get feedback is there anywhere else I can look for clues about this running out of memory error, a log file perhaps.
>
> I am running Suse 11.0 /w KDE 4.1, compiz & emerald. So far everything
> works great except OpenOffice Base as it locks up when I click any
> control.
>
> So I ran it in a terminal to get feedback here is result.
>
>
> Code:
> --------------------
> bolo@linux-mg0v:~> GC Warning: Repeated allocation of very large block
> (appr. size 65536000): May lead to memory leak and poor performance.
> GC Warning: Repeated allocation of very large block (appr. size
> 524288000): May lead to memory leak and poor performance.
> GC Warning: Out of Memory! Returning NIL!
> GC Warning: Out of Memory! Returning NIL!
> Exception in thread “HSQLDB Timer @19af6037” java.lang.OutOfMemoryError
> <<No stacktrace available>>
> GC Warning: Repeated allocation of very large block (appr. size
> 524288000): May lead to memory leak and poor performance.
> GC Warning: Out of Memory! Returning NIL!
> GC Warning: Out of Memory! Returning NIL!
> GC Warning: Repeated allocation of very large block (appr. size 32768000):
> May lead to memory leak and poor performance.
> GC Warning: Out of Memory! Returning NIL!
> GC Warning: Repeated allocation of very large block (appr. size
> 262144000): May lead to memory leak and poor performance.
> GC Warning: Out of Memory! Returning NIL!
> GC Warning: Repeated allocation of very large block (appr. size
> 524288000): May lead to memory leak and poor performance.
> --------------------
>
>
> I have tried installing versions from Suse repo and Openoffice repo and
> both Java 5 & 6 to no avail.
>
> I suspect a java problem but unsure, other Openoffice apps run
> fine.:mad:
>
> Comp= AMD x2 +6000 4gig RAM Asus M2N-SLI Deluxe NVidia 7900GTX
>
>
I’m unable to make my OOo lock up or misbehave in any manner. Perhaps if you
provided the database in question? Or information about the database… was
it created with oobase? How big is it? What exactly are you doing with the
database when it dies?
Are you running 32bit or 64bit SuSE11.0?
This machine is my little one, AMD Semperon 2600+, 1.5GB Ram, NVidia 5500.
Running Suse 11.0, KDE 3.5.9, NO compiz, NO emerald. (Other machine has
better specs)
The GC warning looks to be a warning, nothing else. From what I’ve found,
it’s just the java garbage collector whining about large chunks of ram being
allocated, making its job difficult. (awwww )
Is the error repeatable?
Sounds rather like an interaction between oobase and compiz, emerald or kde
4.1, but no proof really.
Well, this is a long-shot. I had a similar java-memory issue running TuxGuitar. The solution was to install the java-devel package. I have no idea why that helped (and neither did the TuxGuitar developer), but give it a try?
I run OpenSuse 11.0 x64 /w KDE 4.1 and the error happens when I open an existing oobase file (its not very big ) or start a new empty DB and it goes into error as soon as I click any control.
I have uninstalled both Openoffice and Java reinstalling Java 1.5 both x32 & x64 and trying both the OO versions from the suse & openoffice repos in many combos same results so yea its repeatable.
I also have KDE 3.5 & Gnome desktops installed and ooBase does the same in all sessions.
>
> I run OpenSuse 11.0 x64 /w KDE 4.1 and the error happens when I open an
> existing oobase file (its not very big ) or start a new empty DB and it
> goes into error as soon as I click any control.
>
> I have uninstalled both Openoffice and Java reinstalling Java 1.5 both
> x32 & x64 and trying both the OO versions from the suse & openoffice
> repos in many combos same results so yea its repeatable.
>
> I also have KDE 3.5 & Gnome desktops installed and ooBase does the same
> in all sessions.
>
>
{Grin} Well, at least it’s consistent!!
It was suggested to try installing the -devel java packages, the JDK instead
of the JRE.
I’m having the same messsage when using oowriter. The document I’m working on is a simple text document of 8 pages and 9 pictures in it. OOo locks up every time I’m accessing the Picture properties (right-click on picture, “Picture” option from pop-up menu). CPU time and IOwaits hit the roof and the mouse is hardly moving…
I’m using openSUSE 11.0 (up-to-date) on a Dell D630 with dual core CPU and OpenOffice_org-writer-2.4.0.14-1.2.
gnyers wrote:
> I’m having the same messsage when using oowriter. The document I’m
> working on is a simple text document of 8 pages and 9 pictures in it.
> OOo locks up every time I’m accessing the Picture properties
> (right-click on picture, “Picture” option from pop-up menu). CPU time
> and IOwaits hit the roof and the mouse is hardly moving…
>
> I’m using openSUSE 11.0 (up-to-date) on a Dell D630 with dual core CPU
> and OpenOffice_org-writer-2.4.0.14-1.2.
>
> Does that help?
> Regards,
> Gábor
>
>
As has been said, probably JAVA. I had a problem with Calc filling 1.7GB
RAM and 2GB swap in no time flat when I tried to access macros. Finally
found that the JAVA jre, while installed, was not selected in options
(radio button empty) for some unknown reason. No problems since
selecting it.
–
PeeGee
Asus M2V-MX SE, AMD LE1640, openSuSE 11.0 x86-64/XP Home dual boot
Asus M2NPV-VM, AMD 64X2 3800+, openSuSE 10.3 x86-64/XP Home dual boot
I’m having the same messsage when using oowriter. The document I’m
working on is a simple text document of 8 pages and 9 pictures in it.
OOo locks up every time I’m accessing the Picture properties
(right-click on picture, “Picture” option from pop-up menu). CPU time
and IOwaits hit the roof and the mouse is hardly moving…
I’m using openSUSE 11.0 (up-to-date) on a Dell D630 with dual core CPU
and OpenOffice_org-writer-2.4.0.14-1.2.
gnyers wrote:
> I’m having the same messsage when using oowriter. The document I’m
> working on is a simple text document of 8 pages and 9 pictures in it.
> OOo locks up every time I’m accessing the Picture properties
> (right-click on picture, “Picture” option from pop-up menu). CPU time
> and IOwaits hit the roof and the mouse is hardly moving…
>
> I’m using openSUSE 11.0 (up-to-date) on a Dell D630 with dual core CPU
> and OpenOffice_org-writer-2.4.0.14-1.2.
>
> Does that help?
> Regards,
> Gábor
>
>
As has been said, probably JAVA. I had a problem with Calc filling 1.7GB
RAM and 2GB swap in no time flat when I tried to access macros. Finally
found that the JAVA jre, while installed, was not selected in options
(radio button empty) for some unknown reason. No problems since
selecting it.
–
PeeGee
Asus M2V-MX SE, AMD LE1640, openSuSE 11.0 x86-64/XP Home dual boot
Asus M2NPV-VM, AMD 64X2 3800+, openSuSE 10.3 x86-64/XP Home dual boot
)