Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.1.0b1
2018.1.0b2
Issue ID
985809
Regression
Yes
[Speed Tree]Assertion failed error appears when the user stops play mode and profiler window is active.
Assertion failed error appears when the user exits the play mode when billboard renderer component is attached to a speed tree and profiler window is active.
Steps to Reproduce
1. Open the attached project.
2. Open the profiler window.
3. Run the scene and hit stop.
4. Observe that assertion failed error appears in the console.
Reproducible on : 2018.1.0b2, 2018.1.0b1
Works fine on : 2018.1.0a7,2018.1.0a5, 2017.3.0f2
Stack Trace:
Assertion failed: Assertion failed on expression: 'm_CurrentFrame->threadData->m_AllSamples.empty()'
Environment :
Occurring only on Mac
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment