Frame Debugger causes memory leaks

[txanbro]

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?

[CodeSmile]

@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.

[dmnkpv7]

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.