Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.4.X
Votes
5
Found in
2019.3.0a1
2020.1
Issue ID
1194431
Regression
Yes
[Linux] Having same case-insensitive named assets causes infinite import looping
To reproduce:
1) Create a new project
2) Create two sprites in Project Browser
3) Rename them outside of Unity (through Files, for example) so that they're the same name, just with changed case (for example, "square" and "Square")
Expected: Unity either displays one of them or renames it automatically to avoid the identical naming (as OS'es like Windows don't support it)
Actual: An infinite loop is made as it tries to import the two objects. If you rename one of them in Files to break the loop, the project browser is flooded with garbage until you do "Reimport All"
Reproduced in 2019.3.0a1 (although it's much slower here), 2019.3.0b8, 2020.1.0a1, 2020.1.0a11
Not reproduced in 2019.2.5f1, 2019.2.11f1
Comments (2)
-
AdiRishi
Jun 17, 2020 09:28
This happened to me on Unity 2019.4.0 (LTS) just recently.
Looking forward to a fix, happy to help or provide any details I can. -
rk-ba
May 15, 2020 09:07
The same happened for me on Fedora 32, when I focused an object.
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note (fix version 2020.1):
Fixed in 2020.2.0a18
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.5f1