Does Canva's 2024 duplicate‑operation throttle fully reclaim memory after bulk page duplication?

The goal is to verify whether Canva’s 2024 mitigation that throttles duplicate operations and releases unused resources completely eliminates memory growth when a user repeatedly duplicates design pages or elements, especially in workflows involving dozens of slides or high‑resolution assets.

Constraints include variability across browsers and device hardware, the obfuscated nature of Canva’s client‑side code which prevents direct inspection of retained objects, and the absence of any user‑visible setting to manually trigger garbage collection or to diagnose the leak from within the editor. Because the mitigation may only reduce rather than eliminate retention, it remains unclear whether the observed gradual rise is due to lingering references, caching behavior, or a residual leak.

• What specific objects or data structures remain referenced after a bulk duplication sequence?
• Can the throttle parameters be adjusted or temporarily disabled for testing purposes to isolate the leak source?
• Is there a way to expose internal diagnostics, such as a hidden hook or event, that would allow developers to confirm when memory is reclaimed?