topic System Setup Information: in Graphics

OpenGL: GL_OUT_OF_MEMORY error from glUseProgram.

Evan_O_ — Tue, 06 Oct 2015 19:01:21 GMT

I'm seeing a problem with a particular set of shaders that pass structs as 'out' parameters to functions. On a system with Intel Iris 6100 graphics the resulting program generates an OUT_OF_MEMORY error when it is bound with UseProgram. On Nvidia and AMD graphics there is no problem.

I'm attaching a sample program that contains a vertex and fragment shader pair that shows the problem. The application attempts to build a program from them and calls UseProgram and then checks for errors. In debug you should see an assert fire (asserting that there was no error).

I'm testing this on Windows 10 64-bit with driver version 10.18.15.4281.

Thanks,

Evan

Hi Evan,

Michael_C_Intel2 — Tue, 06 Oct 2015 21:39:46 GMT

Hi Evan,

Can you fill in the template below? That with the information you have given me will help us investigate the issue. Thanks for attaching a sample program that is a big help.

System Setup Information:
-----------------------------------------

System Used: (Manufacturer/Model)
CPU SKU: (i3, i5, Pentium, Celeron, etc.)
GPU SKU: (HD4400, HD5100, etc.)
Processor Line: (Y-Series, U-Series, etc.)
System BIOS Version:
CMOS settings:
Graphics Driver Version:
GOP/VBIOS Version:
Operating System:
OS Version:
API:
Occurs on non-Intel GPUs?:

Steps to Reproduce:
-------------------------------
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Expected Results:
-------------------------------

Actual Results:
-------------------------------

Additional Information:
-------------------------------

System Setup Information:

Evan_O_ — Tue, 06 Oct 2015 23:04:05 GMT

System Setup Information:
-----------------------------------------

System Used: Apple, Macbook Pro Retina 13" (2015)
CPU SKU: i7-5557U
GPU SKU: Iris 6100
Processor Line: U series?
System BIOS Version:
CMOS settings:
Graphics Driver Version: 10.18.15.4281
GOP/VBIOS Version:
Operating System: Windows 10
OS Version: 64-bit build 10547
API: OpenGL
Occurs on non-Intel GPUs?: No

Steps to Reproduce:
-------------------------------
1. Build and run attached sample program in debug.
2.

Expected Results:
No GL errors generated by the TestShader function in the application.

Actual Results:
Generates an OUT_OF_MEMORY error.

Additional Information:
-------------------------------

Hi Evan,

Michael_C_Intel2 — Wed, 07 Oct 2015 20:26:41 GMT

Hi Evan,

Thanks for the additional info, I am talking with the OpenGL driver development team and have a ticket filed. We will investigate and find out what is going on.

-Michael

Hi Evan,

Michael_C_Intel2 — Fri, 20 Nov 2015 17:58:37 GMT

Hi Evan,

Do you have a working binary sample for this issue? When we build and run the program nothing is happening, we may be missing some support files.

-Michael

Attached, make sure the vs

Evan_O_ — Fri, 20 Nov 2015 19:08:23 GMT

Attached, make sure the vs.txt and fs.txt files are in the same directory as the exe when you run it (or in the Visual Studio working directory if running from the debugger). The only output will be an assert dialog that glGetError == NO_ERROR.

484530

Got it. Thanks!

Michael_C_Intel2 — Fri, 20 Nov 2015 19:27:02 GMT

Got it. Thanks!

Hi Evan,

Michael_C_Intel2 — Tue, 23 Feb 2016 17:01:19 GMT

Hi Evan,

We found the root cause and fixed the issue in out driver. Now we may not have gotten the fix checked in early enough to make it into the upcoming driver release. So it may not be in the next driver release but the following one.

-Michael

Awesome, thanks for the

Evan_O_ — Tue, 23 Feb 2016 17:38:58 GMT

Awesome, thanks for the update!