-
Notifications
You must be signed in to change notification settings - Fork 29.7k
[dap] Don't use --start-paused when running in Profile/Release mode #98926
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dap] Don't use --start-paused when running in Profile/Release mode #98926
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit. this sentence is awkward. should it be "This is always true for attach requests."?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops! Awkward is an understatement 😄 Fixed!
|
@christopherfujino there doesn't seem to be much info about the failure here: |
|
I'm guessing this was an infra failure, the swarming task page just says "bot died" https://chromium-swarm.appspot.com/task?id=593f4101f7b6cb10&o=true&w=true |
christopherfujino
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. the analysis error will be fixed by rebasing upstream.
This fixes the issue at Dart-Code/Dart-Code#3838 in the SDK DAP server (mirroring a fix made in the legacy Dart-Code DAP server).
This reverts commit 6ec5e51b7c9a5139772e5bb3b8e5b6081783227d.
This change mirrors a fix made in the legacy VS Code extension DAP for Dart-Code/Dart-Code#3838.
The issue is that we were using
--start-pausedin profile mode which would cause a short delay when new isolates were spawned (because they would start paused and wait for us to unpause them). For some measurements of time (including a simple stopwatch) this could make code that uses isolates appear to be slower than it really is.There was no need to use
--start-pausedfor profile mode since debugging functionality is disabled (so we are not concerned about races in setting up breakpoints, etc.) so this simple skips it in those cases.Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.