Editor reserves an excessive amount of memory during Burst compilation when the Profiler window is open

Reproduction steps:

1. Open the attached "IN-147283" project
2. Open Task Manager
3. Switch to the Editor and open the Profiler window (Window > Analysis > Profiler)
4. In the menu bar, navigate to "Burst Repro" > select "Run - WITH Profiler - bug"
5. Switch to Task Manager and observe the Editor "Memory" usage grow until the jobs finish (the message in the Console will appear starting with “END”)

Actual result: The Editor process memory rises by ~5-18 GB
Expected result: The Editor process memory rises by up to ~1 GB

Reproducible with: 1.8.12 (6000.0.0b11) 1.8.29 (6000.5.3f1), 2.0.0 (6000.7.0a2)

Reproducible environment: Windows 11
Not reproducible environment: No other environments tested

Notes:

• Memory may be released when entering Play mode
• Memory may be released when running the Burst test again, following the same growth (within ~10%)
• The Profiler window can be both docked or undocked to reproduce the issue
• Memory usage is 2+ times higher on Burst versions older than 2.0.0 (~16-18 GB vs ~5 GB)