How to reproduce:
1. Open the attached project "HierarchyBugs_H1_H2_H3"
2. Go to QA -> H1 - THE REPRO (different lengths)
3. Observe the Console
Expected results: Renaming the same node over and over does not grow native memory, because each rename replaces the previous name of that one node
Actual results: Native memory grows in proportion to the number of renames - 50000 renames add 1024 KB, 100000 renames add 3072 KB and 200000 renames add 14336 KB - and the memory is never reclaimed
Reproducible with: 6000.6.0f1, 6000.6.1f1, 6000.7.0a6
Not reproducible with: 6000.5.9f1, 6000.6.0b10
Reproducible on: Ubuntu 24.04.4 LTS, macOS Tahoe 26 (M1)
Not reproducible on: No other environment tested
Note: Reproduces identically on Linux and macOS - +1024 / +3076 / +14348 KB on Ubuntu and +1024 / +3072 / +14336 KB on macOS. The two platforms agreeing to within 0.1% shows the growth is deterministic slot-leak arithmetic rather than allocator behaviour.