LWJGL Issues on Ubuntu 11.04 with an ATI Radeon HD 3450

[CodeBunny]

So, I recently acquired a desktop computer, and decided to put an Ubuntu install on it, intending to use it as a development machine. For the most part, that's working, and it's significantly more powerful than the laptop I was using, but I'm having a problem LWJGL.

When I try to run my games in fullscreen, about 95% of the time I get this error:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f34e8109978, pid=6386, tid=139865353082656
#
# JRE version: 6.0_22-b22
# Java VM: OpenJDK 64-Bit Server VM (20.0-b11 mixed mode linux-amd64 compressed oops)
# Derivative: IcedTea6 1.10.2
# Distribution: Ubuntu 11.04, package 6b22-1.10.2-0ubuntu1~11.04.1
# Problematic frame:
# C  [libX11.so.6+0x35978]  XQueryExtension+0x28
#
# An error report file with more information is saved as:
# /home/chris/Game Dev/workspace/Micron/hs_err_pid6386.log
#
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
#   https://bugs.launchpad.net/ubuntu/+source/openjdk-6/
#

Attached is the error log.

What happens is that the game creates a window of the same dimensions of the screen, locks the mouse to it (I can't move the cursor outside the window), and the rendering speed is around 1/2-1/4 of what it should be.

I recently upgraded my drivers to the most recent version, so that shouldn't be causing this.

[jediTofu]

So a quick google search shows it as an error with the X Window system libraries.

I remember posting and/or talking with someone about this I believe.  They ended up finally finding the solution by stopping a certain gnome-applet installed on the main panel by default, but I don't remember what.  Try creating another user and remove all gnome-applet's.  Just have the menu with the start button and that's it, and then try to run it and see if that's the problem.

If that doesn't work, try using sun-java-6 over openjdk/icedtea6.  Also, do an update of your entire system if you haven't.

[CodeBunny]

I'll see what I can do; as to the update, I'm using a copy of Ubuntu I downloaded yesterday.

[CodeBunny]

Doing some more research found this:

http://forum.jogamp.org/SIGSEGV-when-closing-JOGL-applications-td895912.html

I noticed this:

We use 'XInitThreads()' to setup X11 multithreading support
and it seems that the [J]AWT implementation in the JVM calls
X11 functions before and after JOGL runs.

The lack of calling 'XInitThreads()' in the JVM/JRE (when using AWT)
is already identified as a huge pain and a workaround for this
does not seem to be a good idea at all(*).

The best solution would be to convince Oracle/OpenJDK to issue
the XInitThread() call ASAP (before any other X11 call),
and to revisit some _global_ AWT locks, since they are probably no more necessary.
This would allow true inter-component multithreading with X11
without the need of a global AWT toolkit lock and hence
a fluent X11 workflow where threads won't disturb each other anymore.

Does LWJGL do anything like this suggests? This post isn't that old, so conceivably nothing has been done as of yet.

[_ralts]

I've also had this issue with my ATI Mobility Radeon HD 4570 card. When I try to close a window, it always crashes the same message:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fe431879978, pid=1552, tid=140618186254112
#
# JRE version: 6.0_26-b03
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libX11.so.6+0x35978]  XQueryExtension+0x28
#
# An error report file with more information is saved as:
# /home/chris/dev/frangipani/target/hs_err_pid1552.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#

This also happens when I try to close Minecraft, but as I usually don't run Minecraft in a terminal, I didn't realize it until I found the Minecraft directory filled with *.log files 

[Matzon]

crashes outside lwjgl.so are generally not our fault Try updating the drivers