Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2018.4
2019.3.0f1
2019.4
2020.1
2020.2
Issue ID
1251399
Regression
No
Crash on ScriptPlayableOutput::ScriptProcessFrame when running Play Mode test
Reproduction steps:
1. Open user's attached project
2. Press Window > General > Test Runner
3. Select the Play Mode tab
4. Double click on "AnimatorReassignment" to run the test
5. Repeat step 4 (may take 10 times or more)
-- observe crash
Reproducible with: 2018.4.23f1, 2019.4.0f1, 2020.1.0b11, 2020.2.0a13
Note:
1. Stack trace began with ScriptPlayableOutput::ScriptProcessFrame when testing 2018.4.23f1
2.With 2020.2.0a13 Editor.log prints this:
Received signal SIGSEGV
Stack trace:
RtlLookupFunctionEntry returned NULL function. Aborting stack walk.
<Missing stacktrace information>
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a15
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b16
Resolution Note (fix version 2019.4):
Fixed in 2019.4.6f1