Originally Posted by corkiejp
Zygote process is in the system, and should not request root permission (already has it).
You encountered a bug which you should have neither allowed/disallowed and just rebooted your device.
Search the supersu threads, the bug get's reported every now and then.
Well, I've searched for that indeed; but there's no concluding answer that I can spot whatsoever. Anyway, just to see if granting zygote root permission (Chainfire's "suggestion" picked from one zygote related discussion) resulted in any help, I just did... And it positively doesn't. SuperSu has exactly the same bad behavior. I even updated it to 2.82 SR5, to no avail. Nevertheless, I agree this is something that just entered device since SuperSU was working as usual for one month a few days back; I can say it started right after I tried the SuperSU logs section. As of know, I have a nice collection of different "Cracker" logs regarding SuperSU crashes (though, sometimes it just stops). One of the most dramatic SuperSU related events, involved multiple apps and even system stopping in sequence following SuperSU's own. That is something I couldn't even find reports of in any SuperSu nor zygote threads. I think I'll keep trying some stuff before definitely going full restore and start from zero.
Sent from my Moto G4 Plus using XDA Labs