[BUG] [LOCKUP] While microfielding on Sunday, Prime locked up *11* times
I have an Android phone, and it has overlay support. So, I have had Integrated Timer installed for many years. It's a glorified stop-watch. One of the features it has, is that it can have a general-purpose counter. Basically, click the button, and it counts up. Because Prime locks up so frequently(35-45 minutes of play), I added this counter a few days back, to keep track.
There is no repeated sequence of actions that cause it. Recharging, key recycling, gear animations, key carousel, nothing is consistent. Wearing a Programmer Hat, however, I get the feeling that it is not a memory leak, but more of a memory-heap corruption. The nature of the lockup is generally the standard screen-freeze.. Sometimes, however, Prime will just do an immediate exit.

Comments
My 'programmer hat' screams 'mutex order violation'. Most likely callbacks (horrid things to get right) acquiring mutex in the wrong order.
If two things try to do (probably) screen updates there is a deadlock.
So do ANYTHING while walking and it might lock up.
It seems time based, but not wall-clock time. More like number of actions since start.
I cant believe developers can't fix this and the ton of other bugs wich leads to freeze.
I myself suffer of multiple freezes every single day.
When playing 3 or 4 hs i really lost the account how many freezes i suffer.... M
Device:
Moto z2 play, Snapdragon 626 octa-core 2.2GHz, GPU Adreno 506
RAM 4GB
+1, I get a crash pretty consistently every 5-15 minutes of active gameplay. Usually a freeze, but sometimes it dumps to the home screen like you say. The only pattern I've noticed is it is always triggered by a touch event, e.g. pushing a button, and generally happens more frequently the more actions I'm taking.
Pixel 3, Android 10, Ingress 2.36.1
My 'programmer hat' agrees with yours. Would happily put money on this being a concurrency problem of some sort.