Search Issue Tracker
Duplicate
Votes
2
Found in
2022.3.30f1
6000.0.3f1
Issue ID
UUM-72302
Regression
Yes
"StackOverflowException" error when changing spline curve type from "Bezier" to "Auto" in the "Element Inspector"
Reproduction steps:
1. Open the attached “repro_IN-75465“ project
2. Open the “Assets/Scenes/SampleScene.unity“
3. In the Hierarchy, select the “Spline“ GameObject
4. In the Scene view’s toolbar, select the top-located tool for spline editing
5. Click on any of the spline’s edit points
6. In the “Element Inspector“, change from “Bezier“ to “Auto“
Expected result: The selection in the “Element Inspector“ changes from “Bezier“ to “Auto“ without any errors
Actual result: The selection in the “Element Inspector“ changes from “Bezier“ to “Auto“ but “StackOverflowException: The requested operation caused a stack overflow.“ error is thrown
Reproducible with: 2022.3.27f1, 2022.3.30f1, 6000.0.3f1
Not reproducible with: 2021.3.38f1, 2022.3.26f1
Reproducible on: Windows 10 (22H2), macOS Sonoma 14.4.1
Not reproducible on: No other environments tested
Note:
* Reproducible on 2.6.0 version of “Splines” package
* After the error is thrown, the Editor becomes unresponsive (buttons can be highlighted but can’t be pressed)
* On macOS, a silent crash happens, but the Editor.log shows the same “StackOverflowException“ error
Comments (1)
-
chadstonks
May 22, 2024 13:49
Same problem
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note:
Closing this ticket as a duplicate as we have already resolved this issue on the affected versions.
Duplicate of another internal issue: UUM-71488: SetValueWithoutNotify on a TextValueField creates infinite loops and crashes the editor