Probable Memory Leak

[Robigus92]

After a double rotation of the TrainingActivity there are in heap memory 306 instances more of:

class mixedbit.speechtrainer.model.AudioEventCollector$AudioBufferInfoImpl @ 0x1339e4c0

It should not be like this because the rotations return to the same GUI state and the memory should stay in the same state as well. It could be a symptom of a bad management of the onCreate-onDestroy lifecycle.

I have encountered this problem on an Android emulator running 7.1.1 os version.

[Robigus92]

I have found another problem on a different lifecycle event.

After a double background-foreground event of the TrainingActivity there are in heap memory 302 instances more of:

class mixedbit.speechtrainer.model.AudioEventCollector$AudioBufferInfoImpl @ 0x12c051c0

It should not be like this because the background-foreground events return to the same GUI state and the memory should stay in the same state as well. It could be a symptom of a bad management of the onStart-onStop lifecycle.

I have encountered this problem on an Android emulator running 7.1.1 os version.

---

Another problem

After a double pop-up event (e.g. a dialog that covers partially the activity) of the TrainingActivity there are in heap memory 366 instances more of:

class mixedbit.speechtrainer.model.AudioEventCollector$AudioBufferInfoImpl @ 0x1338b4c0

It should not be like this because the pop-up events return to the same GUI state and the memory should stay in the same state as well. It could be a symptom of a bad management of the onPause-onResume lifecycle.

I have encountered this problem on an Android emulator running 7.1.1 os version.