Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.3.0b6
Issue ID
1092355
Regression
No
[DirectX11] Editor flickers and occasionally crashes when continuously generating instances of random prefabs
How to reproduce:
1. Open user-submitted project (WindowsScreenFreezeRepro)
2. Open scene 'Test scene'
3. Enter Play Mode
Expected result: the Editor does not start flickering
Actual result: the Editor starts flickering
Reproducible with: 2018.3.0a5, 2018.3.0b7, 2019.1.0a6
Could not test with: 2018.2.13f1, 2018.3.0a4
Notes:
Only reproducible with Direct3D 11(tested with newest available driver installed)
On some occasions the Editor seems to be working fine until Play Mode is exited, at which point a crash occurs
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
mdeletrain
Oct 24, 2018 15:53
Since it's a DirectX 11 issue, startin gUnity in OpenGL mode allows to temporarily work around the issue.
This is done by adding the -force-glcore switch the shortcut's arguments.