[opensuse] jedit failing on openSUSE 11.0
Hi, I am unable to run jedit on openSUSE 11.0. Here is the error I am getting: ece@srk3:~> jedit GC Warning: Out of Memory! Returning NIL! GC Warning: Out of Memory! Returning NIL! Exception in thread "main" GC Warning: Out of Memory! Returning NIL! java.lang.OutOfMemoryError *** Got java.lang.OutOfMemoryError while trying to print stack trace. The java version is shown below: ece@srk3:~> java -version java version "1.7.0" IcedTea Runtime Environment (build 1.7.0-b24) IcedTea 64-Bit Server VM (build 1.7.0-b24, mixed mode) Any help will be greatly appreciated. Thanks, Koushik. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Sep 25, 2008 at 12:29 PM, Koushik Chakraborty
Hi,
I am unable to run jedit on openSUSE 11.0. Here is the error I am getting:
ece@srk3:~> jedit GC Warning: Out of Memory! Returning NIL! GC Warning: Out of Memory! Returning NIL! Exception in thread "main" GC Warning: Out of Memory! Returning NIL! java.lang.OutOfMemoryError *** Got java.lang.OutOfMemoryError while trying to print stack trace.
The java version is shown below:
ece@srk3:~> java -version java version "1.7.0" IcedTea Runtime Environment (build 1.7.0-b24) IcedTea 64-Bit Server VM (build 1.7.0-b24, mixed mode)
Any help will be greatly appreciated.
Thanks, Koushik. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I have just tried Jedit 4.2 on Opensuse 11, 32-bit, Java 1.6. Seems to work fine (though a bit slow). Have you tried usign Java 1.6 instead? I tend to think 1.7 may be a bit green still. Boris. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I have tried 1.6 from Sun and 1.5 from gij. Both with the same result.
On Thu, Sep 25, 2008 at 10:53 AM, Boris Epstein
On Thu, Sep 25, 2008 at 12:29 PM, Koushik Chakraborty
wrote: Hi,
I am unable to run jedit on openSUSE 11.0. Here is the error I am getting:
ece@srk3:~> jedit GC Warning: Out of Memory! Returning NIL! GC Warning: Out of Memory! Returning NIL! Exception in thread "main" GC Warning: Out of Memory! Returning NIL! java.lang.OutOfMemoryError *** Got java.lang.OutOfMemoryError while trying to print stack trace.
The java version is shown below:
ece@srk3:~> java -version java version "1.7.0" IcedTea Runtime Environment (build 1.7.0-b24) IcedTea 64-Bit Server VM (build 1.7.0-b24, mixed mode)
Any help will be greatly appreciated.
Thanks, Koushik. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I have just tried Jedit 4.2 on Opensuse 11, 32-bit, Java 1.6. Seems to work fine (though a bit slow).
Have you tried usign Java 1.6 instead? I tend to think 1.7 may be a bit green still.
Boris.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I've also been running it (both the stable and development versions) with the Sun 1.6 JDK and it works for me as well. You might try editing the shell script which runs it to increase the max heap and max JVM memory on the java command-line which runs the jedit jar files. That might not fix the real problem, but it could help in getting out a stack trace to see exactly why it's chewing up memory. //ted Koushik Chakraborty wrote the following on 09/25/2008 01:00 PM:
I have tried 1.6 from Sun and 1.5 from gij. Both with the same result.
On Thu, Sep 25, 2008 at 10:53 AM, Boris Epstein
wrote: On Thu, Sep 25, 2008 at 12:29 PM, Koushik Chakraborty
wrote: Hi,
I am unable to run jedit on openSUSE 11.0. Here is the error I am getting:
ece@srk3:~> jedit GC Warning: Out of Memory! Returning NIL! GC Warning: Out of Memory! Returning NIL! Exception in thread "main" GC Warning: Out of Memory! Returning NIL! java.lang.OutOfMemoryError *** Got java.lang.OutOfMemoryError while trying to print stack trace.
The java version is shown below:
ece@srk3:~> java -version java version "1.7.0" IcedTea Runtime Environment (build 1.7.0-b24) IcedTea 64-Bit Server VM (build 1.7.0-b24, mixed mode)
Any help will be greatly appreciated.
Thanks, Koushik. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I have just tried Jedit 4.2 on Opensuse 11, 32-bit, Java 1.6. Seems to work fine (though a bit slow).
Have you tried usign Java 1.6 instead? I tend to think 1.7 may be a bit green still.
Boris.
-- ------------------------------------------------------------------------ *TED MARKOWITZ* /Dept. of Electrical & Computer Engineering and Computer Science Tagliatela School of Engineering University of New Haven West Haven, CT/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Sep 25, 2008 at 1:12 PM, Ted Markowitz
I've also been running it (both the stable and development versions) with the Sun 1.6 JDK and it works for me as well. You might try editing the shell script which runs it to increase the max heap and max JVM memory on the java command-line which runs the jedit jar files. That might not fix the real problem, but it could help in getting out a stack trace to see exactly why it's chewing up memory.
//ted
Ted, This sounds like a good suggestion but I'd still be curious what the real problem was. Boris. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Looking into the jedit script helped. It appears that the environment
JAVA_HOME was set to use gij version of JRE, even though I used sudo
to configure the jre to SUN 1.6 JDK. Once, I set the JAVA_HOME inside
the script, things worked out fine.
Thanks Folks.
On Thu, Sep 25, 2008 at 11:24 AM, Boris Epstein
On Thu, Sep 25, 2008 at 1:12 PM, Ted Markowitz
wrote: I've also been running it (both the stable and development versions) with the Sun 1.6 JDK and it works for me as well. You might try editing the shell script which runs it to increase the max heap and max JVM memory on the java command-line which runs the jedit jar files. That might not fix the real problem, but it could help in getting out a stack trace to see exactly why it's chewing up memory.
//ted
Ted,
This sounds like a good suggestion but I'd still be curious what the real problem was.
Boris.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Boris Epstein
-
Koushik Chakraborty
-
Ted Markowitz