Bug 407143 - Eclipse Crashes as soon as I click anywhere on the file to be edited.
Summary: Eclipse Crashes as soon as I click anywhere on the file to be edited.
Status: CLOSED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.3   Edit
Hardware: PC Linux
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2013-05-03 04:53 EDT by Liam O Donnell CLA
Modified: 2014-07-09 13:39 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Liam O Donnell CLA 2013-05-03 04:53:00 EDT
I started to setup eclipse for the first time on a linux platform (openSuse 12.3).

Within the linux box eclipse runs with no problems.

If I run on a windows box (xp and w7 tried) via putty and xming, eclipse comes up with the active project opened. As soon as I place the cursor in one of the  files to begin editing ...  eclipse crashes ...  displaying a pop up window with the following details.

>>
JVM terminated. Exit code=1
/usr/bin/java
-Dosgi.requiredJavaVersion=1.5
-Dhelp.lucene.tokenizer=standard
-XX:MaxPermSize=256m
-Xms40m
-Xmx512m
-jar /root/Downloads/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
-os linux
-ws gtk
-arch x86_64
-showsplash /root/Downloads/eclipse//plugins/org.eclipse.platform_4.2.2.v201302041200/splash.bmp
-launcher /root/Downloads/eclipse/eclipse
-name Eclipse
--launcher.library /root/Downloads/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120913-144807/eclipse_1502.so
-startup /root/Downloads/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.overrideVmargs
-exitdata 600014
-product org.eclipse.epp.package.java.product
-vm /usr/bin/java
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Dhelp.lucene.tokenizer=standard
-XX:MaxPermSize=256m
-Xms40m
-Xmx512m
-jar /root/Downloads/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar 
<<

Pressing OK to this dialog box, and returning to the terminal screen ... the following message appears

>>
The program 'Eclipse' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 12979 error_code 2 request_code 145 minor_code 26)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
<<


The error log in eclipse shows a Warning in EGit


>>

Warning: EGit couldn't detect the installation path "gitPrefix" of native Git. Hence EGit can't respect system level
Git settings which might be configured in ${gitPrefix}/etc/gitconfig under the native Git installation directory.
The most important of these settings is core.autocrlf. Git for Windows by default sets this parameter to true in
this system level configuration. The Git installation location can be configured on the
Team > Git > Configuration preference page's 'System Settings' tab.
This warning can be switched off on the Team > Git > Confirmations and Warnings preference page.
<<

Note: This does not occur when loading eclipse from within the linux box, only when trying to use eclipse from a remote machine via putty/xming.


Environment:

Linux Box
=========
openSuse 12.3 64 bit (with latest updates)
eclipse Juno (only Regex Util added)
JDK/JRE Java 1.7 u21 installed

Windows Boxes
=============
Xp sp3 32 bit OS
w7 sp1 64 bit os.

Both have putty and xming latest installed

Is this a bug , or is there something I need to configure/change/remove etc.

Regards
Liam
Comment 1 Liam O Donnell CLA 2013-05-21 10:12:42 EDT
Updated putty and xming ... no change

Installed Eclipse Indigo 64bit ... this works.

Although I would prefer the later version of eclipse , I can get by with this for now.

Regards
Liam
Comment 2 Grant Gayed CLA 2013-07-08 16:29:28 EDT
To confirm, Juno (3.8.2/4.2.2) crashes for you, but Indigo (3.7.2/4.1.2) works, right?  And if so, can you try with the recent 4.3 release ( http://download.eclipse.org/eclipse/downloads/drops4/R-4.3-201306052000/index.php )?
Comment 3 Liam O Donnell CLA 2013-07-08 17:49:38 EDT
I installed the latest eclipse as suggested ... unfortunately no change. 

See below similar message to before;

eclipse popup with following message
================
JVM terminated. Exit code=1
/usr/bin/java
-Dosgi.requiredJavaVersion=1.6
-XX:MaxPermSize=256m
-Xms40m
-Xmx512m
-jar /root/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
-os linux
-ws gtk
-arch x86_64
-showsplash /root/eclipse//plugins/org.eclipse.platform_4.3.0.v20130605-2000/splash.bmp
-launcher /root/eclipse/eclipse
-name Eclipse
--launcher.library /root/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20130521-0416/eclipse_1506.so
-startup /root/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.appendVmargs
-exitdata 180010
-product org.eclipse.epp.package.java.product
-vm /usr/bin/java
-vmargs
-Dosgi.requiredJavaVersion=1.6
-XX:MaxPermSize=256m
-Xms40m
-Xmx512m
-jar /root/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
=================

console screen
==============

bus-nagios-dev:~/eclipse # ./eclipse
The program 'Eclipse' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 27866 error_code 2 request_code 145 minor_code 26)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

==============

Regards
Liam
Comment 4 Arun Thondapu CLA 2014-06-25 06:20:13 EDT
Can you please use the latest versions of xming and Eclipse 4.4 (http://download.eclipse.org/eclipse/downloads/drops4/S-4.4RC4-201406061215/ ) and test this again? Thanks!
Comment 5 Arun Thondapu CLA 2014-07-09 13:39:07 EDT
I'm closing this bug report as we're not able to reproduce the problem with Eclipse 4.4 and there has been no response yet to comment 4. Please reopen if you're still able to reproduce the problem.