Gary Roumanis

> Today I'm seeing 50-60 second waits when hitting breakpoints using chrome locally. Is this with just Chrome debugging or using Dart DevTools to debug? I want to understand if...

I can take a look at this later this week. The proper fix isn't too complex either. We'll just need to keep state around so we can properly supply `getStack`.

I took a look at this today and changed the logic so that only the top frame is calculated when returning the paused event [here](https://github.com/dart-lang/webdev/blob/de9fdf0d657acff950cdb0e0c18e15176e7982c3/dwds/lib/src/debugging/debugger.dart#L531). However, it appears that whenever...

This is somewhat related to the Chrome issue. When we hit a breakpoint, or pause execution for that matter, we must translate each JS frame to its corresponding Dart context....

> I tried a few other things - like batching SSE requests between client and server (eg. if the client queues multiple requests while the first is in-flight, the rest...

`webdev` supports a `--verbose` argument which should help capture more detailed logs.

Hmmm. Actually it's not clear to me how we get into this state as we do throw an error if the metadata can't be read: https://github.com/dart-lang/webdev/blob/968e7eb67c3429c07d53ac2a9eba7c5d995fadc2/dwds/lib/src/debugging/metadata/provider.dart#L137 Is it possible that...

It's used to parse the available modules and other related DDC metadata. I think we can sit on this issue until someone reports it with a verbose trace. Hopefully that...

This report is coming from our Flutter analytics. We don't get much more than the stack trace and platform. It's a transient issue so I don't have a repo yet.

I can't find any usage in ACX.