Search Issue Tracker
Duplicate
Votes
0
Found in
2019.3.0a2
2019.3.0a12
2020.1.0a1
Issue ID
1178537
Regression
Yes
[macOS] All the text in the Editor becomes Corrupted and Unreadable after switching to another Window and coming back to Unity
To reproduce:
1. Download attached "App3D.zip" project and open in Unity
2. Open "SampleScene"
3. Enter to Play mode
4. While playing, switch to Rider with the same Unity project opened
5. For a fraction of a second, Rider will show “Updating indices” in the bottom status bar
6. Switch back to the Unity Editor
Expected results: Everything still works as it should
Actual results: Whole Editor window Text became Corrupted and Unreadable
Notes:
- This issue appears only on macOS
- This issue does not happen with Visual Studio
- Some times this issue happens also when rapidly switching to another window and back with Command + Tab
- Picture for reference is attached in Comments section
Reproduced on Unity 2019.3.0a2, 2019.3.0b5 and 2020.1.0a6
Not reproduced on Unity 2018.4.10f1, 2019.2.7f2 and 2019.3.0a1
Regression on Unity 2019.3.0a2
-
bartacuss
Jan 20, 2021 04:56
I am filing the similar issue
However; On my Macbook 16 inch it occurs even when I am simply working in Unity
(don't have to switch windows or app for this to occur)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #1156105