As far as I can tell, this was being caused by two broadcasts being fired back to back.
In that instance, two Fragments
were loaded at the exact same time.
I'm wondering if perhaps for some reason the Fragments were interfering with each other, as the life-cycle states for instantiation etc. would be almost synchronised but ever so slightly "off".
As of now, since I've fixed the problem by ensuring the broadcast happens only once, I'm assuming this is an OS bug caused from an Edge case scenario.