-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
dart:io memory leaks #34724
Comments
Tests failing due to memory leaks in
|
Change-Id: I2b6d03bed48a1d867f95a4c5754d77c7558ae2c6 Reviewed-on: https://dart-review.googlesource.com/c/78780 Reviewed-by: Samir Jindel <sjindel@google.com> Commit-Queue: Daco Harkes <dacoharkes@google.com>
Bug: #32187 Bug: #34724 Change-Id: I123549194670fa5471a187bfcc5e70fd97efc2ee Reviewed-on: https://dart-review.googlesource.com/c/78706 Reviewed-by: Ben Konyi <bkonyi@google.com>
For the future: When gardening and filing issues, please add as much information as possible:
At least one of these leaks are due to:
|
I suspect this has to do with the idle notification implementation: the main thread might be in the process of shutting down while the idle notification task is doing a scavenge The test failure is timing dependent, but it can be reproduced locally (ensure to have built with asan) |
Since this might be the same root cause as #34888 I'm tentatively assinging @rmacnak-google . Hope that's ok. |
Issue #34724 Change-Id: Ia61386939fbb98ae0142c258ae984dd235262fdd Reviewed-on: https://dart-review.googlesource.com/c/81606 Reviewed-by: Martin Kustermann <kustermann@google.com> Commit-Queue: Martin Kustermann <kustermann@google.com> Auto-Submit: Martin Kustermann <kustermann@google.com>
The leak in file_test is being tracked in #40648 Looks like standalone_2/io/signals_test was fixed in another CL. I cannot reproduce the failures in and finally dartk-vm release_x64 lib_2/mirrors/dynamic_load_test - dart:mirrors is not being actively maintained I am closing this issue. If any of the tests in the list do show up with leaks please open new issues with logs that have the error stack trace. |
standalone_2/io/file_test
standalone_2/io/http_server_response_test
standalone_2/io/signals_test
lib_2/isolate/non_fatal_exception_in_timer_callback_test/sleep
The text was updated successfully, but these errors were encountered: