-
Notifications
You must be signed in to change notification settings - Fork 26.8k
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 'not disposed' memory leaks in FF, phase 3. #141198
Comments
CC those who participated in other leak tracking activities. @BlackLeg15, @bivens-dev, @blaugold, @CoderBuck, @cmkweber, @davidmigloz, @Dean-Spotec, @droidbg, @felipecastrosales, @gustav3d, @Harishwarrior, @iapicca, @jayjah, @jogboms, @JohnnyRainbow81, @ksokolovskyi, @Levi-Lesches, @LucasXu0, @Markzipan, @mono0926, @Michal-MK, @navaronbracke, @NobodyForNothing, @noga-dev, @normidar, @p-mazhnik, @philos3, @PiN73, @rei-codes, @resfandiari, @sullenel, @tgucio,@victoreronmosele, @WillianSalceda I am searching for volunteers to help on this issue. |
Working to:
|
@polina-c |
@ksokolovskyi |
…141545) Reverts #141526 Initiated by: CaseyHillers This change reverts the following previous change: Original Description: ### Description - Adds `BoxPainter` creation and disposal events dispatching for memory leak tracking as part of #141198 ### Tests - Updates `decoration_test.dart` to test `BoxPainter` object creation and disposal events dispatching.
Progress check: ~50 laking tests or test files. |
Tagged remaining leaks with [leaks-to-clean]. |
Contributes to #141198 ### Description - Adds `CurvedAnimation` disposals to `material/chip.dart`, `material/input_decorator.dart`, `material/toggleable.dart`, `widgets/animated_switcher.dart`, `widgets/overscroll_indicator.dart`.
CurvedAnimation is leaking a lot. I need to recount leaks after this instrumentation :) |
To repro a leak:
|
See remaining leaks of CurvedAnimation here. |
part of #141198 - Fixes memory leak on `RawDialogRoute` - Adds opt-in test
Part of #141198 *Fixes memory leak on `RangeSlider`*
Unfortunately I solved the problem by downgrading to 3.19.0 on the stable channel. |
@ismailcaakir , can you give more details? Which exact problem do you mean? |
Looking for volunteers to help with this!!! 🚀
Bigger issue: #134787
Goal
Clean up remaining memory leaks (~25) in order to switch to leak monitoring state.
Steps
In general:
if (isLeakTrackingEnabled()) {
in the code and temporary replace it withif (true)
._leak_tracking
and temporarily comment outbringup: true
.a: leak tracking
, remind me, pleaseFix a memory leak:
Identify a leak from one of the sources:
a. flutter dashboard
Look for 3 windows icons on the top left with tooltip ending "leak_tracking".
If one of them have the last execution failing, open its
test stdout
and search forcontains leaks:
.b. Known not-investigated leaky test
Search for
[leaks-to-clean]
in flutter/testc. Not assigned known issue
Assign the issue to yourself.
Investigate the leak.
if
there is a known issue for the leak and it is assignedthen:
add/update TODO for the leak (see template below)else:
(fix the leak) or (create new issue and add the leak TODO to the test)Or instrument a disposable (example):
Templates
Leak tracking opt-out TODO:
Leak tracking opt-in TODO (when tracking is opted out in flutter_test_config.dart or in the entire test file):
Steps to repro (to be copied to issues):
To repro the leak:
References
Issues: all, open, known leaks.
PRs: all, open.
Discord
The text was updated successfully, but these errors were encountered: