# Frame Debugger causes memory leaks

**URL:** https://discussions.unity.com/t/frame-debugger-causes-memory-leaks/1708409
**Category:** Render Pipelines
**Tags:** Scriptable-Render-Pipeline, High-Definition-Render-Pipeline, Bug, 6.3
**Created:** [February 11, 2026, 4:33pm UTC](https://discussions.unity.com/t/frame-debugger-causes-memory-leaks/1708409 "2026-02-11T16:33:20Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![txanbro](https://avatars.discourse-cdn.com/v4/letter/t/ccd318/32.png) [@txanbro](https://discussions.unity.com/u/txanbro)
#### Post date: [February 11, 2026, 4:33pm UTC](https://discussions.unity.com/t/frame-debugger-causes-memory-leaks/1708409/1 "2026-02-11T16:33:20Z")

</div>

I just downloaded version 6.3 LTS yesterday, and I started working on my own framework based on the BatchRendererGroup API. My implementation of object rendering works as expected, but as soon as I enable the Frame Debugger and view the rendering stages, the editor starts to slow down significantly. After a Domain Reload, a memory leak log appears.  
Additionally, these freezes are accompanied by profiler entries that I haven’t seen or noticed before.

It wasn’t until I started preparing screenshots that I realized the issue wasn’t related to my code but rather to the Frame Debugger itself. Even if I run a playmod on an empty scene and enable the Frame Debugger, a memory leak message appears after a Domain Reload.

Is this a bug in the engine version, or am I doing something wrong?

 ![image](https://europe1.discourse-cdn.com/unity/original/4X/d/8/b/d8b21a476a38d316cc98c9c5f5be6e5418598057.jpeg)  
 ![image](https://europe1.discourse-cdn.com/unity/original/4X/e/8/e/e8e3ee71887fadb9b390d5fcb98041dca3ebad60.png)

---

<div class="post-metadata">

### Author: ![CodeSmile](https://dub1.discourse-cdn.com/unity/user_avatar/discussions.unity.com/codesmile/32/82968_2.png) [@CodeSmile](https://discussions.unity.com/u/CodeSmile)
#### Post date: [February 11, 2026, 7:40pm UTC](https://discussions.unity.com/t/frame-debugger-causes-memory-leaks/1708409/2 "2026-02-11T19:40:38Z")

</div>

> [@txanbro](#):
>
> I just downloaded version 6.3 LTS yesterday

You could try 6.3.8f1 which was released today. 😉

Looks like it’s a profiler issue. So best use **Help =\> Report a Bug** to send it in.

---

<div class="post-metadata">

### Author: ![dmnkpv7](https://avatars.discourse-cdn.com/v4/letter/d/7c8e57/32.png) [@dmnkpv7](https://discussions.unity.com/u/dmnkpv7)
#### Post date: [April 6, 2026, 7:43pm UTC](https://discussions.unity.com/t/frame-debugger-causes-memory-leaks/1708409/3 "2026-04-06T19:43:26Z")

</div>

![image](https://europe1.discourse-cdn.com/unity/original/4X/9/5/b/95b51873a10aef8dcd826e7f6575f4e95de4dc5c.png)

I dont know if related but when i updated from 6000.3.0 to 6000.3.8f and now 6000.3.10f the frame debugger became almost unusable (getting 1 FPS) when enabled.