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: https://goo.gl/c0LWYl
See all the talks from Google I/O ’17 here: https://goo.gl/D0D4VE
Subscribe to the Android channel: http://goo.gl/GEh1ds
#io17 #GoogleIO #GoogleIO2017