Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
0
Found in
2019.1.5f1
2019.3
2019.3.12f1
2020.1
2020.2
Issue ID
1242057
Regression
Yes
[HDRP][macOS] Unity crashes when changing Device to Use setting from Automatic to Intel GPU
To reproduce:
1. Open Unity and create an HDRP New Project
2. Open Unity > Preferences...
3. Go to General tab
4. In Device to Use field change setting from Automatic to Intel
Expected results: Unity changes GPU Device to Intel
Actual results: Unity crashes
Notes:
- Stacktrace is shared in Comments section
- Changing Device to Use from Automatic to AMD or from AMD to Intel, doesn't crash Unity
- Sometimes this issue starts to reproducing on all Versions so to stop it you must clear your Cache, but sometimes this also doesn't help
- Maybe it is possible to reproduce this issue on 2020.1.0b7 and 2020.2.0a9, when you test freshly, without clearing or modifying anything
Reproduced on Unity 2019.1.5f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Silicon] Crash on ScriptableRenderLoopJob when machine is left idle while the Editor is in Play mode
- [Android] GraphicsBuffer.CopyCount does not work with Append Compute Buffer after Compute Shader Dispatch on some Android devices
- "DirectoryNotFoundException" error when building a project via script in one folder, then building via Editor in another, deleting the folder built via Editor and rebuilding via Script
- New items are created and old ones remain in memory when using 'treeView.SetRootItems(items)' and 'treeView.Rebuild()' which can cause a memory leak
- Code continues to run after enabling the Frame Debugger when in paused Play Mode and using 'WaitForSecondsRealtime' coroutine
Add comment