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
- Element name field has no character limit in UI Builder
- Async method in Play Mode being aborted when calling `new System.Windows.Forms.Form`
- Animator window Eye button on click visual does not cover the whole area of the button when clicked
- Frame Debugger scrollbar gets cut off at the bottom when the Frame Debugger window is maximised
- Frame Debugger docked with the Game View can still be enabled when Game View is maximised and minimised
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