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

Pattern matching for known native reference leaks #1562

Closed
pyricau opened this issue Sep 5, 2019 · 2 comments · Fixed by #1570
Closed

Pattern matching for known native reference leaks #1562

pyricau opened this issue Sep 5, 2019 · 2 comments · Fixed by #1570

Comments

@pyricau
Copy link
Member

pyricau commented Sep 5, 2019

In API 22 & 23 (maybe others, maybe all) Android will sometimes keep references to Toast.TN through global variables in native code (likely because it's passed through an IPC call).

We need a way to support tagging known leaks caused by native reference leaks

@pyricau
Copy link
Member Author

pyricau commented Sep 8, 2019

Another similar leak: android.view.inputmethod.InputMethodManager$ControlledInputConnectionWrapper is held by a global variable in native code

@pyricau
Copy link
Member Author

pyricau commented Sep 8, 2019

Also com.samsung.android.content.clipboard.SemClipboardManager$1 which would replace all the declarations in SEM_CLIPBOARD_MANAGER__MCONTEXT

pyricau added a commit that referenced this issue Sep 10, 2019
Leaks are often caused by native global variables holding references to live objects. On Android this is super common due to the IPC mechanism holding on to instances until the stub in the other process is garbage collected.

Fixes #1562
@pyricau pyricau added this to the 2.0 Next Release milestone Sep 10, 2019
pyricau added a commit that referenced this issue Sep 10, 2019
Leaks are often caused by native global variables holding references to live objects. On Android this is super common due to the IPC mechanism holding on to instances until the stub in the other process is garbage collected.

Fixes #1562
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant