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
- Standard Unity Materials and Shaders become corrupted after importing specific Asset Packages
- [Linux][OpenGL][Vulkan] Draw calls are not shown in the Event List when taking a capture of a frame with RenderDoc
- Inaccurate collision detections when Rigidbody Collision Detection is set to "Continuous" or "Continuous Dynamic"
- Crash on Object::IncrementPersistentDirtyIndex when upgrading project version
- [iOS] Multiple Xcode project instances created before opens up when performing Build and Run for iOS Platform
Add comment