Access Violation on glReadPixels() with Intel UHD Graphics

[simonem]

Hi,

With the attached simple applications, I get an Access Violation exception on the glReadPixels. Here is the relevant code:

glfwWindowHint(GLFW_SAMPLES, 4);

short* pxData = new short[SCR_WIDTH * SCR_HEIGHT];

//glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);

glReadPixels(0, 0, SCR_WIDTH, SCR_HEIGHT, GL_DEPTH_COMPONENT, GL_SHORT, pxData);

If I don't call glfwWindowHint the exception doesn't occur. 

If I call a glClear before the glReadPixels the exception doesn't occur.

Controller and driver:

Intel UHD Graphics

Driver Version: 31.0.101.2111

The code executes without violation exception when using the NVIDIA GeForce GTX 1650 Ti on the same machine, or on machines with different graphics adapters.

[Steven_Intel]

Hello simonem,

Thank you for posting on the Intel® communities.

In order to better assist you, please provide the following information:

• When did the issue start? Was there any change before the issue started?
• Download the Intel® SSU https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows- 

Open the application and select "Everything", click on "Scan" to see the system and device information. By default, Intel® SSU will take you to the "Summary View". Click on the menu where it says "Summary" to change to "Detailed View". To save your scan, click on "Next", then "Save". Please attach the file to your reply.

Best regards,

Steven G.

Intel Customer Support Technician.

[simonem]

Hello Steven,

I don't know when the issue started. I received reports of sporadic exception from my clients about 1 year ago but this is the first time I managed to systematically reproduce it in a small sample.

Attached is the System Information.

Best Regards,

Simone

[Steven_Intel]

Thank you for your response.

We are going to work on this issue based on the given information. As soon as I have an update, I will let you know.

Best regards,

Steven G.

Intel Customer Support Technician.

[Steven_Intel]

Hello simonem,

In order to continue, please provide the following information:

• Is this a custom application created by you? What is the purpose of this application?
• Could you please provide a step by step to reproduce the issue?
• Is this happening only with 10th generation graphics? By any chance have you tested with newer graphics such as 11th and 12th generation?
• What is the expected behavior we should see if the code runs normally?
• How many systems/clients are affected by the issue?

As well, could you please provide a video showing the issue or how to run the app/codes?

Best regards,

Steven G.

Intel Customer Support Technician.

[simonem]

Hello Steven,

• Yes, it's a custom application created by me, the only purpose is to reproduce the issue.
• I attached a ready-to-use VisualStudio sample in my first post, just open it and run the application to reproduce the exception.
• I don't have 11th or 12th generation graphics to test it, sorry.
• The expected behavior is just not to crash.
• I don't know, most of our client uses a different type of graphics adapters that don't have the issue.

Best Regards,

Simone

[Steven_Intel]

Thank you for the information.

We are going to keep working on this issue. As soon as I have an update, I will let you know.

Best regards,

Steven G.

Intel Customer Support Technician.

[Steven_Intel]

Hello simonem,

So we can continue and replicate the issue, could you please provide the step by step? We need to know how and where should we run the command.

Best regards,

Steven G.

Intel Customer Support Technician.

[simonem]

As I said just open and start the application attached in my first post, have you tried it?

I attached a small video showing the issue.

[Steven_Intel]

Thank you for your response.

We are going to work on this issue. As soon as I have an update, I will let you know.

Best regards,

Steven G.

Intel Customer Support Technician.

[simonem]

Is there any news? Did you replicate the exception?

Sorry, I saw now that you have emailed me but the message ended up in SPAM folder.

Best Regards,

Simone