Repository navigation
webview_flutter memory leak #47992
Copy link
Copy link
Closed
Labels
P3Issues that are less important to the Flutter projectIssues that are less important to the Flutter projectc: performanceRelates to speed or footprint issues (see "perf:" labels)Relates to speed or footprint issues (see "perf:" labels)p: webviewThe WebView pluginThe WebView pluginpackageflutter/packages repository. See also p: labels.flutter/packages repository. See also p: labels.perf: memoryPerformance issues related to memoryPerformance issues related to memoryplatform-iosiOS applications specificallyiOS applications specificallyr: timeoutIssue is closed due to author not providing the requested details in timeIssue is closed due to author not providing the requested details in time
Description
Originally posted by @nuptdzs in #24714 (comment)
with IOS ,I use webview_flutter plugin,I repeatedly enter and exit this page .The memory will grow all the time, and in the leaks tool of Xcode, we can see that a variable is not released after exiting, as shown in the figure below, it seems that some other changes to GL cause this problem.
[✓] Flutter (Channel stable, v1.12.13+hotfix.5, on Mac OS X 10.14.6 18G87, locale zh-Hans-CN)
[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses
[✓] Xcode - develop for iOS and macOS (Xcode 11.3)
[✓] Android Studio (version 3.5)
[✓] VS Code (version 1.38.1)
[!] Proxy Configuration
! NO_PROXY is not set
[✓] Connected device (1 available)
Can you try to analyze this problem, and look forward to your answer. This problem will cause our application memory to grow until it crashes, hoping to give us a solution.
@nuptdzs can you please share a minimal code sample that reproduces the issue?
cc @cyanglaz
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P3Issues that are less important to the Flutter projectIssues that are less important to the Flutter projectc: performanceRelates to speed or footprint issues (see "perf:" labels)Relates to speed or footprint issues (see "perf:" labels)p: webviewThe WebView pluginThe WebView pluginpackageflutter/packages repository. See also p: labels.flutter/packages repository. See also p: labels.perf: memoryPerformance issues related to memoryPerformance issues related to memoryplatform-iosiOS applications specificallyiOS applications specificallyr: timeoutIssue is closed due to author not providing the requested details in timeIssue is closed due to author not providing the requested details in time


Activity
Doris1994 commentedon Jan 10, 2020
I also encountered the same problem,See the previous solution
https://github.com/flutter/flutter/commit/93f339fb67df2934e618cfca0f9d5bd7982e4bcd, flutter version is v1.12.13+hotfix.5.But the problem still exists
owenkealey commentedon Jul 19, 2020
This has been open for 7 months -- am I correct in assuming platform views in flutter have been causing memory leaks for the last seven months?
ycv005 commentedon Oct 24, 2020
Tagging all Webview team: @blasten @TahaTesser @chinmaygarde @jason-simmons Do this issue is fixed ?. It is going to be 1 Year nearly.
danagbemava-nc commentedon Aug 10, 2021
Hi @amirh, can you please confirm if you're still experiencing this issue on the latest flutter
stableandwebview_flutterversion?TahaTesser commentedon Sep 3, 2021
Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of
flutter doctor -v.All system setups can be slightly different, so it's always better to open new issues and reference related issues.
github-actions commentedon Sep 17, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.