Reproduction steps:
1. Open the attached “repro-project” and let it run in the background
2. Open Task Manager
3. Observe the memory usage in the Task Manager

Expected result: Memory usage remains consistent
Actual result: Memory usage slowly rises over time implying that there is a memory leak

Reproducible with: 2022.3.6f1, 2023.1.6f1, 2023.2.0b2
Could not test with: 2021.3.29f1 (due to an error “com.unity.render-pipelines.universal (dependency): Resolved version [12.1.12] does not satisfy requested version [14.0.7]“)

Reproduced on: Windows 10 Pro
Not reproduced on: macOS Ventura 13.4.1 (M1)

Notes:
1. Not reproducible in Player
2. Memory stops increasing when returning back to the Editor and starts again after minimizing it
3. Letting the project run for several hours will cause the Editor to crash with the following first lines of the stack trace:
0x00007ff66ee33a98 (Unity) DynamicHeapAllocator::Allocate
0x00007ff66ee41a3c (Unity) DualThreadAllocator<DynamicHeapAllocator>::Allocate
0x00007ff66ee341b1 (Unity) MemoryManager::Allocate
0x00007ff66ee331ed (Unity) operator new
0x00007ff66f15b2b9 (Unity) AllocateAtomicSafetyNode