rendererAutoProfiler is creating a much bigger performance issue than it is supposedly solving

[axefrog]

Does this issue occur when all extensions are disabled?: n/a (disabling extensions could obfuscate the issue)

• VS Code Version: 1.100.2
• OS Version: Windows 11 Pro (24H2)

Recently I've been experiencing an issue where the whole UI intermittently freezes for a couple of seconds. This can happen sometimes multiple times per minute. Upon investigation, I've observed this message appearing in the console right about the time that the freeze happens:

WARN [perf] Renderer reported VERY LONG TASK (150ms), starting profiling session 'c92f5713-e17a-4691-aa82-a05b22699c15'

Now, 150ms is a far cry short of the intermittent 2-3 seconds of lag I've been experiencing, so I ran a profiling session of my own and observed that the native profiling operation itself appears to be FAR more expensive than the issue it's apparently supposed to be analysing.

Here is a copy of the profiler trace:
Trace-20250520T194245.zip

I am happy to provide additional info if required. I'm not sure what else to offer at this stage though.

[jrieken]

@axefrog Did you enable application.experimental.rendererProfiling on purpose or how did you end up with this?

[axefrog]

@jrieken Yeah it was enabled. I've disabled it and the problem went away. Maybe the issue is still useful feedback for ironing out experimental wrinkles anyway?

[vs-code-engineering]

The described behavior is how it is expected to work. If you disagree, please explain what is expected and what is not in more detail. See also our issue reporting guidelines.

Happy Coding!