Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2017.4.X, 2018.2.X, 2018.3.X
Votes
27
Found in
2017.4.3f1
Issue ID
1039181
Regression
No
"Assertion failed: Failed to insert item" error is thrown when scripts count exceed the limit of 1167 scripts
How to reproduce:
1. Open given Unity project
2. Observe Assertion failed errors
3. Go to Component -> Scripts
4. Notice that not all (3000) scripts are shown here (1167)
Expected result: Either there shouldn't be a limit for scripts or at least one error message should be thrown
Actual result: Error messages are spammed in the console
Reproducible with: 2018.3.0a1, 2018.2.0b4, 2018.1.2f1, 2017.4.4f1, 2017.3.2f1, 2017.2.2p2, 2017.1.4f1
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
- Scene is not rendered and appears black when the Custom Renderer Feature is utilized
- The Context Menu is not updated in the Shortcuts menu when resolving a Binding Conflict
- [Quest] Foveation Level is 0 when SRP Foveation is enabled
- Freeze when displaying text with "-T" in Play mode
- A particle is not rendered for the first frame when the duration and lifetime values match
kuraikage15
Jun 13, 2018 05:16
Is there any fix to get rid of the errors? It''s pretty annoying to see 200+ errors on the console every time I make a build
MiFrilke
Jun 05, 2018 08:34
We started having this issue after the Windows feature update 1803