--
You received this message because you are subscribed to the Google Groups "Chrome DevTools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/4522f151-6f35-4089-a481-96b05fbd45b5n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/077cfa1a-bf3b-464d-aa5e-8e925eba8265n%40googlegroups.com.
I'd have to investigate this particular issue, but guesstimating I'd say chances are good its slow stack trace symbolization again.Would it make sense to permanently add trace events to the v8 inspector for stack trace collection/symbolization? That would make confirmation of these cases easier in the future.On Thu, Oct 22, 2020 at 9:35 AM Simon Zünd <szu...@chromium.org> wrote:I'd have to investigate this particular issue, but guesstimating I'd say chances are good its slow stack trace symbolization again.Would it make sense to permanently add trace events to the v8 inspector for stack trace collection/symbolization? That would make confirmation of these cases easier in the future.
Indeed, one can also compare traces of loading the page with, and without DevTools open to confirm.I'll send a CL.