Community
Participate
Working Groups
Build Identifier: eclipse-SDK-3.6.2-aix-gtk-ppc64 We see this error on most of the client system. The eclipse runs fine for vnc but when using exceed: "The program 'Eclipse' received an X Window System error. This probably reflects a bug in the program. The error message that appeared on the console: "The program 'Eclipse' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 163 error_code 3 request_code 42 minor_code 0) (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."" Since, the problem occurs during the launch of eclipse there were no logs created. Reproducible: Always Steps to Reproduce: All the below steps are done by root user: 1. Connect to an AIX box using Exceed 10.0.0.0 as an XDMCP query. 2. Download eclipse from http://download.eclipse.org/eclipse/downloads/drops/R-3.6.2-201102101200/aixPlatform.php#EclipseSDK. 3. Open a dtterm terminal (like an xterm). 4. Unzip to /opt/eclipse64/ 5. Goto dir /opt/eclipse64/. 6. Launch ./eclipse. Happens all the time on our customer system.
Do you have GTK installed on the system? This is required to be installed prior to using Eclipse on AIX 64-bit.
(In reply to comment #1) > Do you have GTK installed on the system? This is required to be installed > prior to using Eclipse on AIX 64-bit. we do have GTK2-2.10.6-4 installed in addition to the following rpms: cdrecord-1.9-6 mkisofs-1.13-4 popt-1.7-1 rsync-2.6.2-1 openssl-0.9.7l-1 lsof-4.61-4 osinstall-1.0-1 cairo-1.8.8-1 atk-1.12.3-2 expat-2.0.1-2 zlib-1.2.3-4 libxml2-2.6.21-4 freetype2-2.3.9-1 fontconfig-2.4.2-1 gettext-0.10.40-8 glib2-2.12.4-2 libpng-1.2.32-2 libtiff-3.8.2-1 libjpeg-6b-6 xrender-0.9.1-3 xft-2.1.6-5 pango-1.14.5-4 xcursor-1.1.7-3 pixman-0.12.0-3 gtk2-2.10.6-4 vnc-3.3.3r2-6 AIX-rpm-6.1.6.0-8
I don't have access to Exceed 10 but I tried this out on Exceed 11 and I was able to see the crash. Can you try launching eclipse with the -nosplash option (./eclipse -nosplash)? Also, can you also try downloading the 3.7.1 build for AIX 64 and see if the problem shows up there if launched normally? The link for the download is: http://download.eclipse.org/eclipse/downloads/drops/R-3.7.1-201109091335/download.php?dropFile=eclipse-SDK-3.7.1-aix-gtk-ppc64.zip
Can you try launching eclipse with the -nosplash option (./eclipse -nosplash)? I get the following error msg: Failed to load the JNI shared library "/usr/java5/jre/bin/j9vm/libjvm.so" (In reply to comment #3) > I don't have access to Exceed 10 but I tried this out on Exceed 11 and I was > able to see the crash. > > Can you try launching eclipse with the -nosplash option (./eclipse -nosplash)? > > Also, can you also try downloading the 3.7.1 build for AIX 64 and see if the > problem shows up there if launched normally? The link for the download is: > > http://download.eclipse.org/eclipse/downloads/drops/R-3.7.1-201109091335/download.php?dropFile=eclipse-SDK-3.7.1-aix-gtk-ppc64.zip Can you try launching eclipse with the -nosplash option (./eclipse -nosplash)? I get the following error message: Failed to load the JNI shared library "/usr/java5/jre/bin/j9vm/libjvm.so" Also, can you also try downloading the 3.7.1 build for AIX 64 and see if the problem shows up there if launched normally? Ya, the problem still shows up with 3.7.1
Hi, Can you please update the status on this issue. We have clients requesting for a solution. Thanks & Regards, Niraj Singh
Hi, Can you please update the status on this issue. Thanks & Regards, Niraj Singh
Niraj, sent you an email - best thing would be for us to get access to one of your boxes that has the proper version of Exceed in order for us to do some further investigation.
*** Bug 380787 has been marked as a duplicate of this bug. ***
This is happening in Eclipse 4.2 as well any updates on this. This needs to be solved. 32 bit is working well.
Ok -nosplash made it work.
One more thing. The current default xxmaxpermsize of 256m seems to be too little for 64bit systems. I run into outofmemory error very often with this setting. Once I increase this to 512 or 1024 I get no such errors. So consideration for such increase should be given.
I am able to start up eclipse 4.3 without -nosplash option on AIX 7.1, but sometimes encounter a "BadWindow" error. Trying again or adding --sync option would solve the problem as long as I tried. The behavior is same between 32bit and 64bit of eclipse. As Harendra mentioned, I frequently encounter OutOfMemoryError as well as in 4.3. Increasing a maximum heap size to 512m or 1024m does not solve the problem though a frequency of encountering OutOfMemoryError becomes low. I can send a core file and heapdump directly to you if you need so please let me know.
I opened bug 408192 as for OutOfMemoryError.
I received this same error (using the -nosplash), but later realized I did not have access to my configuration data ($HOME/.eclipse). Once I obtained access to my $HOME in shared file space, I was able to invoke eclipse. Thought I would mention it here since it gives the same error message.
SWT no longer provides AIX builds.
