Search Issue Tracker

Active

Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X

Votes

0

Found in

2021.3.31f1

2022.3.13f1

6000.0.10f1

7000.0.0a1

Issue ID

UUM-54445

Regression

No

Editor that is opened using a command line with a "-force-gles" argument crashes on DrvPresentBuffers when closing the Editor on Windows with an NVIDIA RTX A2000 GPU

--

-

Reproduction steps:
1. Open the Command Prompt
2. Open the attached "PROJECTFILE" project by using a command line in the Command Prompt: "C:\Program Files\Unity\Hub\Editor\2021.3.31f1\Editor\Unity.exe" -projectPath PROJECTPATH -force-gles
3. Quit the Editor

 

Repro steps:
* start a new project with 2D URP template
* Set Graphics API to OpenGLES
* in the HUB, return the licence, while the is still open
* go back to the Editor - you'll get a pop-up that will force you to close the editor
* notice that instead of an elegant shut-down, you get a crash. In the Editor.log, the same stack trace appears.

I have Windows 11 and the ThinkPad Extreme X1 Gen 3 Laptop. 
GPU: GeForce GTX 1650 Ti

Reproduced on 6000.0.10f1 and 2021.3.40f1

Expected result: Editor closes without crashing
Actual result: Editor crashes

Reproducible with: 2021.3.31f1

Reproducible on: Windows 11
Not reproducible on: macOS Ventura 13.6 (M1 Max)

First few lines of the stack trace:
0x00007ffa677537f6 (nvoglv64)
0x00007ffa67b5b5fe (nvoglv64) DrvPresentBuffers
0x00007ffa67abfbf4 (nvoglv64) DrvDeleteContext
0x00007ffb0efd3f0c (OPENGL32) wglDeleteContext
0x00007ff62242c2f9 (Unity) CleanupMasterContext
0x00007ff622435621 (Unity) GfxDeviceGLES::~GfxDeviceGLES
0x00007ff622435844 (Unity) GfxDeviceGLES::vector deleting destructor'

Note: The issue was reproduced with an NVIDIA RTX A2000 GPU

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.