Can we say that the code is not good enough?
Here's a piece of analytical data on memory consumption by one Android application. How do you know, surges down are Java's garbage collection.
If the swings were sharper, it would be possible to conclude that there was a clear presence in the code of memory leaks and, in principle, the ineffective use of memory.
But what can you say from these data? Can we clearly say how economical/neutral memory is going to be?
The code is pretty big, it doesn't make sense, but it's worth pointing out that it predominates operations to set up small-scale masturbating facilities up to 30 seconds.
This example (the same annex after optimization attempts) can be considered as less effective use of memory than the example above:
Actually, it's not good practice to rely on a garbage collector. If the destruction of obvious objects is to be compared to the same schedule, but with more aggressive debris collection policies. If the comparison of leaks is not visible, it can be argued that leaks are not available. But it's better to look at the code as well as install the meters.