Closed
Description
Steps to Reproduce
- Start Flutter app.
- Push several pages the Navigator
- Pop several pages.
- In Xcode use Debug Memory Graph to capture memory graph
- In memory filter the leaks.
leaks
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel xy_beta_v0.5.6, v0.5.6-pre.112, on Mac OS X 10.13.5 17F77, locale zh-Hans-CN)
[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
[✓] Android Studio (version 3.1)
[✓] VS Code (version 1.25.1)
[✓] Connected devices (1 available)
• No issues found!
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
xster commentedon Aug 30, 2018
cc @cbracken for routing
cbracken commentedon Aug 30, 2018
/cc @bkonyi who worked on our BoringSSL integration and may have thoughts.
/cc @jason-simmons who may also have thoughts on this; I'd be curious if we see the same issue on Android.
bkonyi commentedon Aug 30, 2018
Is it possible to provide a full backtrace for the allocation? It looks like we're deep into BoringSSL but it's hard to tell at which point we entered the library and where we're leaking memory.
nightwolf-chen commentedon Aug 31, 2018
It looks like the memory was leaked when allocating memory for SSL certificate.
xster commentedon Sep 1, 2018
@nightwolf-chen, can you copy-paste the whole backtrace stack?
nightwolf-chen commentedon Sep 3, 2018
nightwolf-chen commentedon Sep 3, 2018
nightwolf-chen commentedon Sep 3, 2018
nightwolf-chen commentedon Sep 3, 2018
@xster I've posted several backtrace for most significant memory leaks. I hope that helps you understand the SSL memory leak problem.
bkonyi commentedon Sep 28, 2018
Quick status update: we haven't found the exact cause of the majority of the leaked memory here, but we have a hunch that this may be an issue with BoringSSL. Someone familiar with the BoringSSL internals is going to look into it more closely next week.
7 remaining items