Search Issue Tracker
Fixed
Fixed in 6000.3.8f1, 6000.4.0b8, 6000.5.0a6
Votes
4
Found in
6000.4.0b1
6000.5.0a3
Issue ID
UUM-130076
Regression
Yes
"Script updater for [...] failed with exitcode [...] and stdout: Stack overflow." errors thrown in console when a project using obsolete API is opened
How to reproduce:
1. Open the attached "IN-125325_ArguException.zip" project in Safe Mode
2. Observe the console
Actual result: Errors about the script updater failing and related script errors are thrown in the console
Expected result: No errors appear in the console
Reproducible with: 6000.4.0a4, 6000.4.0b1, 6000.5.0a3
Not reproducible with: 6000.0.64f1, 6000.2.15f1, 6000.3.0f1, 6000.4.0a3
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- In a clean project, the same errors appear after importing "_PoiyomiShaders" assets from the attached project
- On the version 6000.5.0a3 only errors related to Timeline appear in the console: "Script updater for Library\Bee\artifacts\1900b0aE.dag\Unity.Timeline.Editor.dll failed with exitcode -2147023895 and stdout: Stack overflow.", while the version 6000.0.4b1 displays more - the same one, a similar one related to shader graph and several script errors
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
- Nothing happens when entering a converter ID to target property in the Add Binding window when a converter ID was already added and removed
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- [Linux] Numeric field value stops increasing when cursor reaches the edge of the monitor while dragging
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
Resolution Note:
Fixed in 6000.5.0a6
Resolution Note (fix version 6000.5.0a6):
Fixed in 6000.5.0a6