How to reproduce:
1. Open the “IN-89082.zip“ project ([https://drive.google.com/drive/folders/1h4A0JN-HU9W2tbhM3GH5aBO688NNjrHu?usp=sharing])
2. Open the “Interlaminar - Observer Web App“ Scene (The scene name is mentioned in the comments)
3. Select the “Adaptive Probe Volume“ GameObject in the Hierarchy
4. In the Inspector, click the “Bake Probe Volumes“
5. Open the Task Manager
6. Wait until the baking seemingly finishes
7. Observe the Task Manager and the Console

Expected results: APVs get baked successfully, memory is released, and nothing is logged in the Console
Actual results: APVs fail to bake, memory is not released, and an “OutOfMemoryException“ is logged in the Console

Reproducible in: 6000.0.47f1, 6000.1.0b15, 6000.2.0a9
Could not test in: 2022.1.0a1, 2022.3.61f1 (No Adaptive Probe Volumes)

Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested

Notes:
- The memory starts building up on the “subdividing cells” portion of the process
- Canceling the baking process during “subdividing cells” does not release the memory either
- Locally tested on a machine with 32GB of RAM

Investigation notes:
* This happens during _placement_ which is part of preparing for baking. When there are 191.983.481 probes in a batch, and thus in a Dictionary<int, int>, adding another entry to the dictionary will cause it to grow beyond 2GB.
* Lifting that restriction will cause {{ApplySubdivisionResults}} to return 212.734.475 positions in a {{NativeList<Vector3>}} with {{Capacity}} = 268.435.456.
* This will then hit an integer overflow bug in {{{}NativeList<T>.NativeArray(){}}}; it should try to {{UnsafeUtility.MemCpy}} 2.552.813.700 bytes, but due to the integer overflow bug it will try to copy -1742153596 bytes.