- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I did an example program on procedural textures and found out that on our school computers the program crashes in the driver.
We have following configuration:
CPU i5 3330
GPU HD 2500
OpenGL driver 10.18.10.4425
Our program is written in Java 1.8 SE using LWJGL framework and crashes in the native code of the driver where the program gets through glLinkProgram. It seems that the driver has problems with compilation of smoothstep function inside the fragment shader. When the smoothstep function is not used, the program does not crash. The program is in the attachment.
Expected behaviour: 640x480 empty white window.
Real behaviour: crash.
Stack trace:
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [ig7icd32.dll+0x3f1367]
C [ig7icd32.dll+0x2a2c97]
C [ig7icd32.dll+0x2a5358]
C [ig7icd32.dll+0x38e6ac]
C [ig7icd32.dll+0x38ed2a]
C [ig7icd32.dll+0x120697]
C [ig7icd32.dll+0x38f738]
C [ig7icd32.dll+0x120686]
C [ig7icd32.dll+0x38ea8f]
C [ig7icd32.dll+0x120697]
C [ig7icd32.dll+0x38ea8f]
C [ig7icd32.dll+0x1207c5]
C [ig7icd32.dll+0x38f14d]
C [ig7icd32.dll+0x120697]
C [ig7icd32.dll+0x38ea8f]
C [ig7icd32.dll+0x120697]
C [ig7icd32.dll+0x34d805]
C [ig7icd32.dll+0x34d72a]
C [ig7icd32.dll+0x1a9cc7]
C [ig7icd32.dll+0x11daaf]
C [ig7icd32.dll+0x11ea2a]
C [ig7icd32.dll+0x11ebd2]
C [ig7icd32.dll+0x238592]
C [lwjgl_opengl32.dll+0x12285]
j org.lwjgl.opengl.GL20.glLinkProgram(I)V+1
j cz.muni.fi.pv112.smoothstep_bug.Bug.loadProgram(Ljava/lang/String;Ljava/lang/String;)I+37
j cz.muni.fi.pv112.smoothstep_bug.Bug.loop()V+12
j cz.muni.fi.pv112.smoothstep_bug.Bug.run()V+37
j cz.muni.fi.pv112.smoothstep_bug.Bug.main([Ljava/lang/String;)V+7
v ~StubRoutines::call_stub
V [jvm.dll+0x158f95]
V [jvm.dll+0x21e54e]
V [jvm.dll+0x15902e]
V [jvm.dll+0xdb007]
V [jvm.dll+0xe359f]
C [java.exe+0x228d]
C [java.exe+0xae9f]
C [java.exe+0xaf29]
C [kernel32.dll+0x1336a]
C [ntdll.dll+0x39902]
C [ntdll.dll+0x398d5]
C 0x00000000
The "crash" stack trace gets created in the program folder when the program crashes.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
The issue is specific to HD 2500? If so there is not much I can do, there are no planned driver releases for HD 2500. So if it is a driver issue I can't get a fixed driver. Sorry.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Sorry, I really don't know about other GPUs as we have only those HD2500s on i5-3330s. I can understand that you do not plan a new driver release but I cannot understand that you do not want to cope with such a serious issue (when confirmed). The 3rd generation Intel CPUs (2012) are still widely used. What about the software companies? How should they explain to their customers/users?
And yes, most times we can do workarounds. But what about the situation when also the workarounds get broken? Sorry, you got paid for your devices, so I see such an attitute as irresponsible.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page