SummaryThe application is experiencing significant performance degradation and slow load times. The logs indicate that the garbage collector (GC) is running frequently and for extended periods, blocking memory allocation. This suggests a potential memory leak or high memory churn within the application.LogsThe following logs show frequent GC activity and blocking:

I/s.iturn.trainer(23991): Background concurrent copying GC freed 133MB AllocSpace bytes, 18(31MB) LOS objects, 51% free, 90MB/186MB, paused 48us,38us total 436.682ms
I/s.iturn.trainer(23991): WaitForGcToComplete blocked Alloc on Background for 161.600ms
I/s.iturn.trainer(23991): WaitForGcToComplete blocked Alloc on Background for 161.770ms
I/s.iturn.trainer(23991): WaitForGcToComplete blocked Alloc on Background for 162.094ms
I/s.iturn.trainer(23991): WaitForGcToComplete blocked Alloc on Background for 160.523ms
I/s.iturn.trainer(23991): Background young concurrent copying GC freed 65MB AllocSpace bytes, 9(5096KB) LOS objects, 37% free, 116MB/186MB, paused 44us,44us total 102.625ms
I/s.iturn.trainer(23991): Background young concurrent copying GC freed 33MB AllocSpace bytes, 2(1440KB) LOS objects, 18% free, 152MB/186MB, paused 74us,40us total 141.753ms