UPDATE 25/10/2025:

The user-submitted project is for 6000.1.4f1 so to make this easier to validate in the re-spin of 2022.3.62f3, I've attached a new project that easily reproduces the issue.

• Unzip the attached "UUM-108093-LEAKTEST.zip"
• Load the "LeakTest" scene and hit "Play"
• Observe the "Allocated: XXX MB" value in the bottom-right of the Editor (see attached "UUM-108093-LEAKTEST.png" image)

Expected: It stays (approximately) at the same value

Actual: The value climbs without end, eventually leading to a crash due to the Editor running out of memory.

Using 2022.3.62f2 we leak memory whereas using 2022.3.62f3 that incorporates a fix that landed in 2022.3.64f1 does not.

—

Original User Message:

When running Rigidbody physics on WebGL, “Unknown” in the memory profiler keeps increasing.
Even after destroying the Rigidbody, the memory is not released.

1. Launch the program
2. Instantiate several objects
3. Wait for a short period
4. Take a snapshot with the profiler
5. Check "Unknown" under "All of Memory"

Disabling the simulated property of the Rigidbody2D prevents the memory increase.
Therefore, I concluded that the issue is related to 2D physics calculations.

It might also be occurring in the editor, but since I am checking it using WebGL diagnostics, I am treating it as a WebGL issue.