-
Notifications
You must be signed in to change notification settings - Fork 324
"Unresponsive extension host" opening large project #4326
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
Comments
Whenever we discover a test, we do this: Dart-Code/src/shared/test/test_model.ts Lines 439 to 440 in 686c268
This rebuilds the parent, which means for a group with lots of tests, we're rebuilding all the siblings. But we then rebuild the entire suite, which not only duplicates all of that work, but then also does it for the rest of the file. The intention here is to ensure the parent statuses are up-to-date, but seems like maybe we could a) avoid the duplicated work, b) walk up instead of down to avoid doing more nodes then we need to, c) do we even need to update any status here? Can a newly-discovered test even change any parent statuses since it has the lowest status? (it's possible we need to rebuild the parent in order to replace its |
While looking into #4325, with
f32_test.dart
open and running "Reload Window" to restart, I see this in the console:Several profiles here:
cpu profiles.zip
The text was updated successfully, but these errors were encountered: