bluenote10
commented
8 years ago I have tracked down the problem and can now offer a minimal reproducing example. The problem is caused by a small "loading" splash screen that is shown during the OpenGL initialization. It looks like there are some kind of side effects between LWJGL/GLFW and Java Swing. In can reproduce the problem like this (I hope it is okay to post in Scala, let me know I should provide a Java version):
import java.awt.BorderLayout
import java.awt.Color
import javax.swing.ImageIcon
import javax.swing.JFrame
import javax.swing.JLabel
import org.lwjgl.glfw.GLFW.glfwInit
class SplashScreenMinimal extends JFrame {
val icon = new ImageIcon(getClass().getClassLoader().getResource("animated.gif"))
val label = new JLabel(icon)
getContentPane().add(label, BorderLayout.CENTER)
// transparent frames must be "undecorated"
setUndecorated(true)
// in general the following allows to use transparency in an animated gif,
// but this seems to trigger the problem:
setBackground(new Color(0, 0, 0, 0))
pack()
setLocationRelativeTo(null)
setVisible(true)
def close() {
setVisible(false)
dispose()
}
}
object SplashScreenMinimal {
def main(args: Array[String]): Unit = {
val splashscreen = new SplashScreenMinimal()
// now glfwInit will crash
glfwInit()
}
}It looks like the splash screen must satisfy a few conditions in order to trigger the RenderBadPicture (a regular JFrame is not an issue):
- The background of the frame must have an alpha value != 255. Not using
setBackgroundat all or settingsetBackground(new Color(0, 0, 0, 255))does not crash, but e.g.setBackground(new Color(0, 0, 0, 254))fails. - Apparently, the frame must display some kind of graphics like an
ImageIcon. In my case it was an animated GIF with transparency. It looks like it is not necessary for the GIF to be transparent though (crashed with this one as well). A transparent PNG also seem to crash.
Now the question is: Why and how does LWJGL 3 or GLFW interfere with this Swing stuff? I'm not sure if this really is a LWJGL bug, but at least this code seem to work in general and also with LWJGL 2.
Spasi
kappaOne
pierr3
ShadowLordAlpha
Ali-RS
fleather
I'm currently facing a very weird issue: In one of my projects I'm getting the following error during initialization. My initialization code is pretty much identical to the Pong example code, with added logging statements to see the steps of the initialization:
The reason for the vague statement "during initialization" is that the error seems to be asynchronous, and it is not always happening in
glfwCreateWindow. For instance, this is output of another run, where I somehow made it past theglfwCreateWindow:Note that the error in this case also comes with an additional
pure virtual method called, which is not the case when it happens in other places.Another example: If I don't call
glfwInitright at the start of the main function, the error always seems to be triggered byglfwInititself, i.e., I do not get to the point of setting the error callback etc. I was actually very surprised to see that the behavior changes depending on whether I placeglfwInitbefore or after the other initialization code, because this other code has nothing to do with OpenGL / native libraries and just initializes a few Java/Scala data structures.I do get this error with both the latest stable build (build #3.0.0b build 64) and the latest nightly (build #3.0.0 build 41). My system is an Ubuntu 14.04, 64bit, Java 1.8.0_74, Nvidia Geforce GTX 670, Nvidia driver version 352.79.
What makes this issue even more annoying is the fact that it seems to be difficult to reproduce: So far, I get this error only in my main project. I was trying to come up with a minimal example to reproduce it, but in the minimal example the exact same code works. I'm currently trying to add some complexity from the big project to the minimal example to see what may trigger the problem. But even after adding all dependencies and using exactly the same JVM options, I could not reproduce the error so far. I'm now looking into other potential side effects...
I should add: I have just ported the big project from LWJGL 2.9.1 to 3.X for the first time. With 2.9.1 everything was working fine.
Any hints what could possibly go wrong would be highly appreciated.