Search Issue Tracker
Fixed
Votes
0
Found in
2023.3.0b9
Issue ID
UUM-65091
Regression
Yes
Crash on memset_repstos when entering Play Mode
Reproduction steps:
1. Open the attached “repro-project“
2. Enable the Debug Allocator (Edit → Preferences → Diagnostics → Core → enable ForceDebugAllocator → Restart Editor)
3. Open the “Assets/AstarPathfindingProject/Developer/_Scenes/UnitTests.unity“ scene
4. Enter Play Mode
5. Observe the crash
Reproducible with: 2023.3.0b1, 2023.3.0b9
Not reproducible with: 2021.3.35f1, 2022.3.20f1, 2023.2.12f1, 2023.3.0a19
Reproduced on: Windows 10
Not reproducible on: No other environment tested
Notes:
1. The debug allocator enhances the predictability and clarity of the bug's stack trace. However, the issue can be replicated without it, albeit with a less clear stack trace and less often
2. Could not test the Player due to Build completing with a result of 'Failed'
First few lines of the stack trace:
0x00007FFBDED5EA39 (Unity) memset_repstos
0x00007FFBDC9D301E (Unity) RaycastCommandJob
0x00007FFBDC204AF6 (Unity) ujob_execute_job
0x00007FFBDC203E61 (Unity) lane_guts
0x00007FFBDC206804 (Unity) worker_thread_routine
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
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
- Element name field has no character limit in UI Builder
- Async method in Play Mode being aborted when calling `new System.Windows.Forms.Form`
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-65085