Skip to content
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

fix(android): destroy webView to prevent memory leak #1014

Closed
wants to merge 1 commit into from

Conversation

jessyefuster
Copy link

Platforms affected

Android

Motivation and Context

Fixes #290

Description

Testing

Checklist

  • I've run the tests to see all new and existing tests pass
  • I added automated test coverage as appropriate for this change
  • Commit is prefixed with (platform) if this change only applies to one platform (e.g. (android))
  • If this Pull Request resolves an issue, I linked to the issue in the text above (and used the correct keyword to close issues using keywords)
  • I've updated the documentation if necessary

@jessyefuster jessyefuster deleted the 290-destroy-leak branch August 16, 2023 10:51
@jessyefuster jessyefuster restored the 290-destroy-leak branch August 16, 2023 15:36
@jessyefuster jessyefuster deleted the 290-destroy-leak branch August 16, 2023 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

InAppBrowser will not destroy WebView after being closed (by invoking ref.close()) causing memory leaks
1 participant