Search Issue Tracker
Fixed
Fixed in 2021.3.16f1, 2022.2.0b15, 2023.1.0a13
Votes
0
Found in
2020.3.36f1
2021.3.6f1
2022.1.8f1
2022.2.0a19
2023.1.0a2
Issue ID
UUM-8679
Regression
No
Crash on EvaluateSlow when running particle system
How to reproduce:
- Open the user attached project
- Add the CRASH prefab to Hierarchy
- In Hierarchy select Canvas -> Button
- In the Inspector's Button Component, drag the child GameObject in the CRASH prefab into the OnClick event in the Button.
- Set the Button Function to test > Test (int)
- Enter Play Mode
- Click the Button
- The editor crashes
Reproducible with: 2020.3.36f1, 2021.3.6f1, 2022.1.8f1, 2022.2.0a19, 2023.1.0a2
Note: If the Button is not visible change the Aspect Ratio
Reproduced on: Windows 10 (Intel)
First lines of stack trace:
0x00007ff68ba294c2 (Unity) EvaluateSlow
0x00007ff68cb99e6d (Unity) UpdateOrbitalAndRadialTpl<4,0,0>
0x00007ff68cbab493 (Unity) VelocityModule::Update
0x00007ff68ba3b0d0 (Unity) ParticleSystem::UpdateModulesPreSimulationIncremental
0x00007ff68ba355c5 (Unity) ParticleSystem::StartModules
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2023.1.0a13):
The fix is to display an error and not crash.
The setup is invalid - we don't support the XYZ curves using different modes (ie they must all be curves, or all floats, not a mixture)
We handle this for all other modules that use XYZ curves, but had missed some error handling here.
So you should update your code to use the same mode for all 3 orbital velocity curves.