Unable to destroy own opengl context after calling Unigine::Engine::init

[sebastian.vesenmayer]

We run into a problem with an AMD Radeon RX 6800 graphics card when shutting down our application.

When we call Unigine::Engine::init with our own created opengl context the next call to "wglDeleteContext(m_context);" crashes in the graphics driver.

When we are not calling Unigine::Engine::init we are able to destroy the opengl context normally.

This happens with Qt Opengl Context and build from scratch Windows OpenGL context.

We don't know what is happening in the init call with te opengl context, but maybe you can tell us?

NVidia graphics cards work.

Thanks.

Edited July 2, 2021 by sebastian.vesenmayer

[sebastian.vesenmayer]

This is the unigine log file log.txt of the run.

[silent]

Hi Sebastian,

Any test code for the reproduction? Do you have issues only with RX6800 or any other Radeon GPU?

Maybe there is some easier workaround that we can find on our side.

Vendors are not paying much attention to OpenGL these days, so it can be easily some AMD driver issue that would take years to fix :(

Thanks!

[sebastian.vesenmayer]

Hi silent,

minimal reproducer is in preparation.

We only have one Radeon for testing right now.

 

[sebastian.vesenmayer]

Hi silent,

I stripped the application heavily, now it works, so I think some of our application code is breaking some objects on the heap. I will investigate this further.

Thanks

[sebastian.vesenmayer]

Hello silent,

we have found the setting which causes the application to crash during opengl context destruction.

When <show_profiler>1</show_profiler> is set in default.user config it crashes.

<show_profiler>0</show_profiler> works.

We also tried to disable profiler during runtime, but it has no effect on the shutdown crash.

I will upload a minimal reproducer example to your ftp.

Thanks

[sebastian.vesenmayer]

Hello, are there any updates on this issue?

[silent]

We will try to do a second attempt soon, but so far we didn't find any valid clues.

There are several usual suspects:

• OpenGL (oof!)
• OpenGL AMD driver
• OpenGL and custom contexts
• OpenGL and (???)

Hope that new attempt would be more productive.

Thanks!

[sebastian.vesenmayer]

Ok thanks for the update, you told me something about an error the nvidia driver did output in our example. What was it?

[silent]

That also subject for investigation (there is a possibility that it's not related to your code). So right now we don't have any specific findings.

[silent]

@sebastian.vesenmayer

It also looks like there is no crashes anymore with the latest AMD GPU driver: Radeon™ Software Adrenalin 21.10.3.

Can you check that on your side as well?

[sebastian.vesenmayer]

Thanks I will check this driver ASAP