My application leaks Bitmaps of random shapes that I don’t have in my drawable folder

Question

I have a strange memory leak problem where my application continues to stream Bitmap objects and other objects related like VectorDrawables , AnimationDrawables

I have an Eclipse Memory Analyzer , and Gimp was able to recover missing Bitmap objects and found that they are random shapes of stars, as well as squares or circles. I do not have these shapes in the res/drawable .

Where do they come from and why do they leak so much? This leak occurred on my Samsung Galaxy S7 - Android 7.0 and on an emulator with Android 7.0 and 6.0. But there are no leaks when starting my application on the go Huawai Android 4.4.4

Here is the link to my hprof. if someone comes closer: https://www.dropbox.com/s/e1ry3ny5eb66xk8/out3%20-%20Kopi.hprof?dl=0

Screenshot from Dominator tree from memory analyzer

They are marked in yellow, for example, the stars below this image.

Raster image of stars found in my leaks

Also my stack rate continues to spit endlessly

  03-21 17:00:08.415 16747-16747/muddzdev.shoppist I/InputMethodManager: [IMM] startInputInner - mService.startInputOrWindowGainedFocus 03-21 17:00:08.428 16747-16760/muddzdev.shoppist D/InputTransport: Input channel constructed: fd=98 03-21 17:00:13.315 16747-16886/muddzdev.shoppist E/OpenGLRenderer: saveGfxinfoFileDisabled enabled 03-21 17:00:13.632 16747-16886/muddzdev.shoppist E/OpenGLRenderer: saveGfxinfoFileDisabled enabled 03-21 17:00:13.914 16747-16886/muddzdev.shoppist E/OpenGLRenderer: saveGfxinfoFileDisabled enabled 03-21 17:00:14.257 16747-16886/muddzdev.shoppist E/OpenGLRenderer: saveGfxinfoFileDisabled enabled 03-21 17:00:14.592 16747-16886/muddzdev.shoppist E/OpenGLRenderer: saveGfxinfoFileDisabled enabled 03-21 17:00:14.933 16747-16886/muddzdev.shoppist E/OpenGLRenderer: saveGfxinfoFileDisabled enabled 03-21 17:00:15.299 16747-16886/muddzdev.shoppist E/OpenGLRenderer: saveGfxinfoFileDisabled enabled 

Answer 1

So this problem is so difficult to debug, and it took me a whole week to work on it. This leak did not come out, and CanaryLeak cannot detect it.

I deleted Android Studio, deleted all recovery folders on the computer under AppData in your User folder, and everything else related to Android or Android Studio under your C:/User and Program files and even the SDK folder.

I did a complete registry cleanup using CCleaner , and then downloaded Android Studio again, cloned my project from Git, and then launched the application again and here it is! NO LEAKAGE FOR EVERYONE.

I am pretty sure that this crazy leak has nothing to do with your own application, but something with Android Studio or something completely different.

Answer 2

I had the same problem with S7 after upgrading to API 24, I was able to remove this error by turning off the GPU monitor in Android Studio. It seems like this is definitely a problem with android studio, perhaps only with S7.