Search Issue Tracker
Won't Fix
Won't Fix in 1.0.X
Votes
0
Found in [Package]
1.0.0
Issue ID
ECSB-109
Regression
No
Crash on profiling::ProfilerUnsafeUtility::BeginSample when exiting Play Mode
Reproduction steps:
1. Open the user’s attached project
2. Enter Play Mode
3. In Game View, click “Start Simulating”
4. In Game View, click “Enable Rollback Tests”
5. Wait for 20 seconds
6. Exit Play Mode
Expected result: Exited the Play Mode
Actual result: Unity Editor crashes
Reproducible with: 1.0.0-exp.8 (2022.2.0b12, 2023.1.0a15)
Couldn’t test with: 0.17.0-preview.42 (project breaks because com.unity.entities.graphics is not supported in lower versions)
Reproducible on: Windows 1 Pro 21H2
First lines of the stack trace:
{noformat}0x00007ff651e7035c (Unity) profiling::ProfilerUnsafeUtility::BeginSample
0x00007ff6512c715d (Unity) ProfilerUnsafeUtility_CUSTOM_BeginSample
0x00000236d4adde11 (Mono JIT Code) (wrapper managed-to-native) Unity.Profiling.LowLevel.Unsafe.ProfilerUnsafeUtility:BeginSample (intptr)
0x00000236d4addc9b (Mono JIT Code) Unity.Profiling.ProfilerMarker/AutoScope:.ctor (intptr)
0x00000236d4addadb (Mono JIT Code) Unity.Profiling.ProfilerMarker:Auto (){noformat}
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
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
Resolution Note:
Hey hey!
I cannot reproduce your crash after removing the use of the deprecated, and broken method EntityManager.DestroyAndResetAllEntities() The world copying code that the sample uses does not complete successfully as it relies on destroying managed objects from within jobs that are scheduled internally (which was broken behaviour in the ECS and was deprecated as such). It is recommended to use a supported version of Entities, 1.0.x, or 1.1.x. How the project is setup currently will lead to generating indeterminate state by not resolving the many safety exceptions the current project throws when run as is.
Resolution Note (1.0.X):
Hey hey!
I cannot reproduce your crash after removing the use of the deprecated, and broken method EntityManager.DestroyAndResetAllEntities() The world copying code that the sample uses does not complete successfully as it relies on destroying managed objects from within jobs that are scheduled internally (which was broken behaviour in the ECS and was deprecated as such). It is recommended to use a supported version of Entities, 1.0.x, or 1.1.x. How the project is setup currently will lead to generating indeterminate state by not resolving the many safety exceptions the current project throws when run as is.