tree: 1707f144a1fbc449d1013941bf6638add55f8878 [path history] [tgz]
  1. .vscode/
  2. android/
  3. ios/
  4. lib/
  5. linux/
  6. macos/
  7. test/
  8. web/
  9. windows/
  10. .gitignore
  11. .metadata
  12. analysis_options.yaml
  13. pubspec.yaml
  14. README.md
case_study/memory_leaks/leaking_counter_1/README.md

leaking_counter_1

This is memory leaking application to test memory debugging tools.

Leak debugging lab

  1. Setup the lab:

    a. Start the latest version of DevTools by following BETA_TESTING.md

    b. in another console tabs navigate to the DevTools directory (cd devtools) and start the app:

     cd case_study/memory_leaks/leaking_counter_1
     flutter run -d macos --profile
    

    c. Copy the Observatory URL displayed in the console to the connection box in DevTools

  2. Solve the puzzle:

Users report the app consumes more and more memory with every button click. Your task is to fix the leak using the tab Memory > Diff, assuming the application is too large to find the issue by simply reviewing the code of the button handler.