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.

Sign up for GitHub

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

Jump to bottom

data leak in com.google.android.gms.common.data.DataHolder #44

Open
stolk opened this issue Dec 18, 2016 · 1 comment
Open

data leak in com.google.android.gms.common.data.DataHolder #44

stolk opened this issue Dec 18, 2016 · 1 comment

Comments

@stolk
Copy link

stolk commented Dec 18, 2016

A data leak is reported for com.google.android.gms.common.data.DataHolder

W/GamesServiceBroker( 1907): Client connected with SDK 8115000, Services 10084030, and Games 39080030
I/ActivityManager(  953): Killing 7873:com.sec.android.app.mss/u0a26 (adj 15): empty #43
W/GamesServiceBroker( 1907): Client connected with SDK 8487000, Services 10084030, and Games 39080030
W/GamesServiceBroker( 1907): Client connected with SDK 8487000, Services 10084030, and Games 39080030
E/DataBuffer( 1907): Internal data leak within a DataBuffer object detected!  Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: com.google.android.gms.common.data.DataHolder@42b732c8)
V/GamesNativeSDK( 8346): Play Games callback indicates connection.
I/GamesNativeSDK( 8346): Successfully connected to Google Play.
@claywilkinson
Copy link
Contributor

Thanks, I'll pass it along to the SDK team.

@chrisbabcock-epic chrisbabcock-epic mentioned this issue Sep 27, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@stolk @claywilkinson