- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello there! I'm not sure if this is the right board for this, so I apologize in advance if it is not.
I'm working on an OpenGL Windows application and my program is crashing in the igxelpicd64.dll driver thread when I don't call the SwapBuffers function after calling the glClear and glClearColor functions in the main loop. The crash occurs after a certain amount of time has passed, not immediately, which is why I believe there might be some kind of race condition at play.
Here is some pseudocode. If you would like, I can you with provide more debug information and the full source code or pre-compiled executable files of my application. You will need MSVC and CMake to build the project.
#include "my_opengl_loader_which_definitly_not_related_to_segfault.h"
#include "my_window_library_which_sure_not_related_to_issue.h"
int
main(void)
{
// Window creation
// Render context initialization
// Loading functions from opengl32.dll
while (1) {
glClear(...);
glClearColor(0, 0, 0, 1);
#if !defined(WANT_SEGFAULT_IN_IGXELPICDDLL)
SwapBuffers(GlobalDeviceContext);
#endif
}
}
Here is my software and hardware information:
Operating System: Microsoft Windows 11 Home 10.0.22631
IGCC Version: 1.100.5635.0
Language: en-US
Physical Memory: 15.73 GB
Current Resolution: 2880x1800
Processor: 12th Gen Intel(R) Core(TM) i5-12500H
Processor Speed: 2500 MHz
GFX Driver Name: Intel® Iris® Xe Graphics
Shader Version: 6.6
OpenCL* Version: 3.0
* Microsoft DirectX* *
Runtime Version: 12
Hardware-Supported Version: 12
Vendor ID: 8086
Device ID: 46A6
Device Revision: 0C
GFX Driver Version: 31.0.101.4502
Dedicated RAM: 128 MB
Shared RAM: 8 GB
Max Supported Displays: 4
GFX Vulcan: 1.3.250
GFX GOP: 21.0.1046
* Digital Display 1 *
Display Name: Built-In Display
Display Type: Digital
Serial Number: -
DDC2 Protocol: Supported
Gamma: 2.2
Connector Type: DisplayPort
Maximum Image Size
Horizontal - 11.81 inches
Vertical - 7.48 inches
Supported Modes
2880 x 1800 (60p Hz)
2880 x 1800 (90p Hz)
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, gr3yknigh1.
Thank you for posting in our Community.
It looks like you're dealing with an interesting issue, and I think you're on the right track with your analysis. Based on your description, it's possible that the crash is related to how OpenGL handles the buffer swap in relation to your render context, especially if "SwapBuffers" is not being called. It might indeed be a timing issue, which could be a sign of a race condition or an issue with synchronization between the CPU and GPU.
In the meantime, I'll need to conduct some additional research on this issue and will post an update in this thread as soon as I have more information. Regarding the full source code, feel free to share it along with any debug information or even a pre-compiled version. I'd be happy to take a closer look and assist with troubleshooting further.
Have a nice day!
Best regards,
Von M.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello! Thank you for your response and your time.
Here are the full source code and two pre-compiled binaries: one that calls Swapbuffers and one that does not. I have also added some notes in the README.txt file.
Have a great day!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, gr3yknigh1.
Thank you for your response and for providing the source code and the pre-compiled binaries. To assist you further and investigate this issue more effectively, could you please provide the following information:
- What is the name of the OpenGL Windows application and the program where the crash occurred?
- Are you the developer of this program, or is this a third-party application?
- Please update the graphics driver to version 32.0.101.6297, as the version 31.0.101.4502 you mentioned is not the latest release. You can download the updated driver here: Intel® Arc™ & Iris® Xe Graphics - Windows
- Was the application working fine before? If so, when did the issue first start occurring?
- If the problem persists after updating the driver to version 32.0.101.6297, could you kindly provide the latest SSU logs for further analysis?
Looking forward to your response.
Best regards,
Von M.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, gr3yknigh1.
I'm following up to check whether you have had the chance to review our prior correspondence. If you have, kindly acknowledge receipt and let me know if you need time to share the details I asked for. Please let me know about this information so we can identify the next steps that need to be taken to resolve this issue.
I will wait for your reply.
Best regards,
Von M.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I apologize for the delay in responding. This week has been busy, and I also had difficulty logging into this forum using my credentials. There was some strange error at the login page.
Regarding your previous question:
1. A crash occurred in a separate thread of the igxelpicd64.dll Windows driver while my application was running.
2. As I explained in my initial question, I am developing a game engine based on OpenGL rendering.
3. I tried updating my drivers before with some Intel apps (probably called "Intel Driver & Support Assistant"), and also tried updating with an app from my laptop vendor (Lenovo). However, the issue still persisted (and I have reported it here after all the updates). I will try again this week and let you know the results.
4. In the past, Intel drivers have crashed in other cases, but it was due to my fault with the render context initialization. I didn't have enough knowledge to properly report the problems there. This time, I was able to reproduce and isolate the problem to a single line of code, so I decided to report it.
5. Of course! When I update all my graphics drivers, I will try to reproduce the issue.
Thank you for your time! Again, I apologize for the delay in my response. Have a great day!
Best regards, Ilya A.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page