-
Notifications
You must be signed in to change notification settings - Fork 23
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
Clean up notDisposed leaks in Flutter Framework, phase 1. #134
Comments
progress check: 2071 tests are converted |
@polina-c Where do we track that all required widgets/services do
in their constructor? |
Yes, not all extenders of ChangeNotifier do this at the moment. Feel free to just add it where you need. |
@polina-c Could you please take a look at this PR, which adds tracking to the ScrollController: flutter/flutter#133759 ? |
progress check: 3458 tests covered |
@ksokolovskyi , I updated description asking to communicate subset of tests where you plan to work. |
@polina-c, nice, thanks. |
progress check: 5223 tests are converted |
I'm currently not actively working on this, but some PRs are still open. |
@polina-c I also like to contribute to this. |
@droidbg, yes and thank you! |
covered: 8826 |
@polina-c I have raised PRs for test/gesture and test/painting, could you please review it. |
@polina-c I have raised PRs for test/rendering (all TCs are done), could you please review it. |
@droidbg I used to work on test/cupertino feel free to continue it. Here are some notes about the unconverted tests I still have: A PR for cupertino/date_picker_test is still open. The following files are not converted and have undisposed widgets:
Once flutter/flutter#134661 is completed, you should be able to cover I don't know about any other unconverted tests but you should probably check for yourself in case I missed something. |
Will appreciate votes here: flutter/devtools#6266 (comment) @NobodyForNothing @ksokolovskyi @droidbg @navaronbracke |
FYI, update on leak_tracker progress: https://discord.com/channels/608014603317936148/1106667330093723668/1162097704462196788 |
Hello folks, these are the updates on the subsets I was working on:
@polina-c |
98% are covered!!! @ksokolovskyi, @droidbg , @NobodyForNothing , I greatly appreciate your help! Closing this issue in favor of the next phase, where help is also needed and appreciated: flutter/flutter#137311 |
Yes, pick any class or test-set in flutter/flutter#137311 |
Looking for volunteers to help with this!
Subtask of: flutter/devtools#3951
Issues: all, open.
PRs: all, open.
All invocations of
testWidgets
under flutter/test (~ 10,000) should be converted to testWidgetsWithLeakTracking by iterating the steps:Comment on this issue what subset of tests you plan to work on so that we do not duplicate work. Then delete the added comment as soon as you are done or if your plans changed. If all tests seems to be occupied, let me know, and I will redistribute them.
Convert set of
testWidgets
, create PR and, if tests pass, request review and merge. Example: Cover more tests with leak tracking. flutter/flutter#132806For tests that fail, investigate them and search for the culprit class name in onen issues or PRs (check links above). If the issue for this concrete leak is already created or PR is on the way, leave this test to be 'testWidgets'. Otherwise, move the conversion to a separate PR, and do one of two in this PR:
a. Fix the failure if it is strait-forward.
b. Create issue that explains the leak, create allowlist, and link the issue near the allowlist. Example: Mark leak in text_form_field_test.dart. flutter/flutter#130468. Then either allow triage process to happen or assign the issue to yourself and resolve it in a separate PR.
Link the issue and the fix in a comment for this PR.
Do not:
Focus areas:
@ksokolovskyi: test/widgets
@droidbg: test/paintings, test/rendering and test/gestures
@NobodyForNothing: paused (thank you for what is done and in process)
@polina-c: coordinating complicated cases and integration with testWidgets
Discord calls: 1, 2
Thread on discord for leak_tracker updates
The text was updated successfully, but these errors were encountered: