Bug? Might Unity in single thread mode create a new UnityMain in some edge case?

Hi guys,

Our development involves diving into the Android platform when running Unity base Apks.

We have stumbled upon a situation in which an app set to not be multi threaded sometimes starts a second UnityMain if we:

1. Non-MT-Unity app A is set as a default Android launcher.
2. A calls non-MT-Unity app B (A is not quitting - just moved to background as we call app B intent with "startActivity").
3. B is focused.
4. B is being quit.
5. A (default launcher unity app...) crashes and we notice a new UnityMain thread.

NOTE: when the crash does not happen (it only occurs every several attempts) - there is no second UnityMain thread.

Is there any known condition in which Unity process will try to start a second UnityMain thread even though the app was set to not be multi-threaded?

 

Level 1 bump.