Why are there hundreds of bitmaps in memory for the main Android application?

Question

When creating my first Android application, I noticed that memory usage was already approaching 20 MB immediately after launching the application. I downloaded Mcl Eclipse and looked through the contents to find hundreds, if not thousands, of bitmaps in memory. Many of them are not used directly in my project (at least not so much that I know)

Largest image - 9 MB: https://imagebin.ca/v/2eCK4JYLO2f2

Others are much smaller: https://imagebin.ca/v/2eCMmbFuIWsz

Android seems to have gone long distances to reduce memory using zygote ... so why are so many unused bitmaps already in memory?

(The main project is an empty activity using Android Studio with a fragment consisting of a text view that simply says "Hello World!")

Answer 1

I found that the bitmaps were taken from the Zygote memory area. Since all Java-based applications run through zygote, this means that the minimum memory usage is determined by the size of memory used by Zygote, which, in turn, is based on the display density of the device.

Answers found:
Find a class that takes memory
Find and fix the cause of the large heap size