Search Issue Tracker
Fixed in 2018.1.X
Fixed in 5.6.X, 2017.1.X, 2017.2.X, 2017.3.X
Votes
0
Found in
2018.1.0a1
Issue ID
961692
Regression
Yes
Asserts and possible leak appear when enabing specific Skinned Mesh Renderer in play mode
Reproduction steps:
1. Open project attached (ClothAnimationCrash.zip).
2. Enter play mode.
3. Enable Skinned Mesh Renderer (Plane->PlaneAnimation&Clot->Plane04->Skinned Mesh Renderer).
Expected result: Skinned Mesh Renderer will be shown, the console will stay clean.
Actual result: Error "Assertion failed" appears with a warning "JobTempAlloc has allocations that are more than 4 frames old.."
Full error message: Assertion failed: Assertion failed on expression: 'Thread::EqualsCurrentThreadIDForAssert(Thread::mainThreadId)'
Notes: After about 30 seconds, objects fall from the sphere and another "bunch" of errors are spammed in the console. Before entering play mode, make sure to have object "PlaneAnimation&Cloth" or its Skinned Mesh Renderer disabled.
Reproduced on: 2018.1.0a1.
Works fine on: 5.5.4p4.
Could not test on other versions due to another issue.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Add comment