Chrome v114 slowdowns due to enabling Debugger in dev tools

[vibaldem]

We started seeing this in our private instance, due to this bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1428605#c20
Compile Scripts task can take up to 10x longer when debugger or 'disabled-by-default-v8.cpu_profiler' is on due to expensive calls to collect source positions.

As far as I can tell, debugger is on to prevent pausing and to collect script ids for initializer matching. The latter doesn't seem to get affected with debugger off, so is that data just for backup? Are there any other possible effect to turning debugger off?