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/ExampleScenes/Scenes/InfiniteWorld/InfiniteWorld.unity“ scene
4. Enter Play Mode
5. Move the GameObject called "Bot CharacterController" around the Game View
6. Observe the crash

Reproducible with: 2023.3.0a2, 2023.3.0b7
Not reproducible with: 2021.3.35f1, 2022.3.20f1, 2023.2.0a23, 2023.2.12f1
Could not test with: 2023.3.0b8, 2023.3.0b9 (due to another bug UUM-65060)

Reproduced on: Windows 10
Not reproducible on: No other environment tested

Notes:
1. Gradual memory increase can be observed in the Task Manager during runtime
2. 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
3. Could not test the Player due to Build completing with a result of 'Failed'

First few lines of the stack trace:
0x00007FFE4E4EB870 (Unity) PhysicsCommands::Physx::CollectorOverlapCallback<64>::processTouches
0x00007FFE504670ED (Unity) physx::NpSceneQueries::multiQueryphysx::PxOverlapHit
0x00007FFE5047AAC4 (Unity) physx::NpSceneQueries::overlap
0x00007FFE4E4E78D4 (Unity) PhysicsCommands::Physx::OverlapWithCollector
0x00007FFE4E4E2915 (Unity) OverlapCapsuleCommandJob

0x00007FFB1DA6E2CD (Unity) OverlapCapsuleCommandJob
0x00007FFB1D2B0D06 (Unity) ujob_execute_job
0x00007FFB1D2B0071 (Unity) lane_guts
0x00007FFB1D2B2A14 (Unity) worker_thread_routine
0x00007FFB1D46E595 (Unity) Thread::RunThreadWrapper