| Eclipse 2.1 Crashes Regularly - JVM Exit Code 134 [message #193722] |
Thu, 20 January 2005 15:54  |
Eclipse User |
|
|
|
Originally posted by: scott.nospam.telesoft.com
I've been running Eclipse 2.1 on my RedHat 9 box for a couple of years
now. It routinely crashes once or twice each week - sometimes more,
sometimes less. There's never been any rhyme or reason to what I'm
doing when it happens. I've had it happen during edit sessions, CVS
commit, switching between tabs, etc. It's all over the place. When it
crashes, I get the following output:
JVM terminated. Exit code=134
/usr/java/j2sdk1.4.2_03/bin/java
-Xmx192m
-cp /home/scott/eclipse/startup.jar org.eclipse.core.launcher.Main
-os linux
-ws gtk
-arch x86
-showsplash /home/scott/eclipse -showsplash 600
Has anyone else experienced this and if so, is there any resolution?
Thanks.
|
|
|
|
| Re: Eclipse 2.1 Crashes Regularly - JVM Exit Code 134 [message #193802 is a reply to message #193722] |
Fri, 21 January 2005 10:23  |
| Eclipse User |
|
|
|
Originally posted by: kcollins.pinksheets.com
I've run 2.1, all of the 3.0M series up 3.1M4 on Linux without any
crashes. I'm using Debian testing. I'm working with two other developers
using Linux (RedHat and Mepis) with 2.1 and 3.0, and they haven't had
any problems over the last year either.
You may consider upgrading to the latest stable version of the Gnome and
gtk libraries and see if that helps. It also wouldn't hurt to give
Eclipse more than 192m.
On Thu, 2005-01-20 at 13:54 -0700, Scott Dudley wrote:
> I've been running Eclipse 2.1 on my RedHat 9 box for a couple of years
> now. It routinely crashes once or twice each week - sometimes more,
> sometimes less. There's never been any rhyme or reason to what I'm
> doing when it happens. I've had it happen during edit sessions, CVS
> commit, switching between tabs, etc. It's all over the place. When it
> crashes, I get the following output:
>
>
> JVM terminated. Exit code=134
> /usr/java/j2sdk1.4.2_03/bin/java
> -Xmx192m
> -cp /home/scott/eclipse/startup.jar org.eclipse.core.launcher.Main
> -os linux
> -ws gtk
> -arch x86
> -showsplash /home/scott/eclipse -showsplash 600
>
>
> Has anyone else experienced this and if so, is there any resolution?
>
> Thanks.
|
|
|
|
|
| Re: Eclipse 2.1 Crashes Regularly - JVM Exit Code 134 [message #194123 is a reply to message #193737] |
Mon, 24 January 2005 15:13 |
| Eclipse User |
|
|
|
Originally posted by: scott.nospam.telesoft.com
Phillip Beauvoir wrote:
> That's Linux for you...
>
> Try using an OS that works - like Windows.
That's why I run Linux - thanks, but no thanks. :-)
I've been running/using Windows since it's inception (when it was an app
running on DOS) and had already been a Unix user for 5 or 6 years prior.
So - as far as true operating systems go, and being knowledgeable of
both, I'll take any Unix hands-down over Windows.
Also - Eclipse is the only Java app with which I've experienced any
problems on this platform. I also run Oracle, Tomcat, Resin, etc. - no
prob.
>
> ;-)
>
>
> "Scott Dudley" <scott@nospam.telesoft.com> wrote in message
> news:csp5pu$2rf$1@www.eclipse.org...
>
>>I've been running Eclipse 2.1 on my RedHat 9 box for a couple of years
>>now. It routinely crashes once or twice each week - sometimes more,
>>sometimes less. There's never been any rhyme or reason to what I'm doing
>>when it happens. I've had it happen during edit sessions, CVS commit,
>>switching between tabs, etc. It's all over the place. When it crashes, I
>>get the following output:
>>
>>
>>JVM terminated. Exit code=134
>>/usr/java/j2sdk1.4.2_03/bin/java
>>-Xmx192m
>>-cp /home/scott/eclipse/startup.jar org.eclipse.core.launcher.Main
>>-os linux
>>-ws gtk
>>-arch x86
>>-showsplash /home/scott/eclipse -showsplash 600
>>
>>
>>Has anyone else experienced this and if so, is there any resolution?
>>
>>Thanks.
>
>
>
|
|
|
| Re: Eclipse 2.1 Crashes Regularly - JVM Exit Code 134 [message #194197 is a reply to message #194123] |
Tue, 25 January 2005 08:08 |
| Eclipse User |
|
|
|
Originally posted by: p.beauvoir.bolton.ac.uk
Sorry if it came out wrong.
Irony.
Phil
"Scott Dudley" <scott@nospam.telesoft.com> wrote in message
news:ct3ktq$guc$1@www.eclipse.org...
> Phillip Beauvoir wrote:
>> That's Linux for you...
>>
>> Try using an OS that works - like Windows.
>
> That's why I run Linux - thanks, but no thanks. :-)
>
> I've been running/using Windows since it's inception (when it was an app
> running on DOS) and had already been a Unix user for 5 or 6 years prior.
> So - as far as true operating systems go, and being knowledgeable of both,
> I'll take any Unix hands-down over Windows.
>
> Also - Eclipse is the only Java app with which I've experienced any
> problems on this platform. I also run Oracle, Tomcat, Resin, etc. - no
> prob.
>
>>
>> ;-)
>>
>>
>> "Scott Dudley" <scott@nospam.telesoft.com> wrote in message
>> news:csp5pu$2rf$1@www.eclipse.org...
>>
>>>I've been running Eclipse 2.1 on my RedHat 9 box for a couple of years
>>>now. It routinely crashes once or twice each week - sometimes more,
>>>sometimes less. There's never been any rhyme or reason to what I'm doing
>>>when it happens. I've had it happen during edit sessions, CVS commit,
>>>switching between tabs, etc. It's all over the place. When it crashes,
>>>I get the following output:
>>>
>>>
>>>JVM terminated. Exit code=134
>>>/usr/java/j2sdk1.4.2_03/bin/java
>>>-Xmx192m
>>>-cp /home/scott/eclipse/startup.jar org.eclipse.core.launcher.Main
>>>-os linux
>>>-ws gtk
>>>-arch x86
>>>-showsplash /home/scott/eclipse -showsplash 600
>>>
>>>
>>>Has anyone else experienced this and if so, is there any resolution?
>>>
>>>Thanks.
>>
>>
|
|
|
Powered by
FUDForum. Page generated in 0.07117 seconds
Home