How to Manage Native C++ Memory in Android (Google I/O ’17)

Android native applications typically use Java objects that “own” C++ objects. When the Java garbage collector detects that the Java object is no longer needed, the Java object either explicitly deallocates the C++ object, or decrements its reference count. Choreographing this Java-C++ interaction can be subtle, and mistakes can result in hard-to-diagnose memory corruption. We’ll point out interesting pitfalls, and provide advice for avoiding them. If you are an Android C++ developer, you don’t want to miss this talk.

Watch more Android talks at I/O ’17 here:
See all the talks from Google I/O ’17 here:

Subscribe to the Android channel:

#io17 #GoogleIO #GoogleIO2017

via Android Developers

About The Author
- Welcome to the Android Developers channel on YouTube. This is the home for Android Developers Live videos from our live events, as well as for videos containing demos, tutorials, and anything else related to Android development.

Tell us what you think...