Search Issue Tracker
Fixed in 5.5.3
Votes
0
Found in
5.5.2p1
Issue ID
888339
Regression
Yes
Crash in InitWGL when opening project with -force-opengl command
To reproduce:
1. Run Unity with -force-opengl commad
2. Create new or open attached project
3. Unity crashes
Reproducible: 5.5.0p4, 5.5.2p1, 5.6.0b11, 2017.1.0a2
Not reproducible 5.3.8f1, 5.4.3p3 (Both versions crashes with RtlLookupFunctionEntry returned NULL function. Aborting stack walk.<Missing stacktrace information>)
Reproduced on Windows 10
Stack Trace:
0x0000000141509094 (Unity) InitWGL
0x0000000141509B36 (Unity) CreateContextGL
0x0000000141509F6C (Unity) CreateMasterGraphicsContext
0x00000001417B9F02 (Unity) GfxDeviceGLES::Init
0x00000001417B223D (Unity) CreateGLESGfxDevice
0x000000014096A112 (Unity) CreateRealGfxDevice
0x00000001409DFBA8 (Unity) GfxDeviceWorker::Startup
0x00000001409F0D18 (Unity) CreateClientGfxDevice
0x000000014096BECF (Unity) InitializeGfxDevice
0x00000001411F01AB (Unity) InitializeEngineGraphics
0x0000000141495A3E (Unity) Application::InitializeProject
0x000000014155B737 (Unity) WinMain
0x00000001418768C4 (Unity) strnlen
0x00007FFED4FE8364 (KERNEL32) BaseThreadInitThunk
0x00007FFED59470D1 (ntdll) RtlUserThreadStart
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leak when a lot of UI elements are spawned and despawned
- Warnings are not logged in the Console window when using external code analyzers
- Errors “TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations, size 288“ appear constantly when Prefab is open
- Crash on PPtr<Shader>::operator or NullException errors spammed in console when calling Dispose() on null GraphicsBuffer with baked Reflection Probes
- “EndRenderPass: Not inside a Renderpass” and other Render Graph errors in the Player when Render Graph is enabled and Overlay UI is used
Add comment