I presume this is a reference to the facts of the recent huge thread

https://news.ycombinator.com/item?id=29492884

Yes -- this is a follow-up investigation into how that bug might have occurred by looking at recent commits to AOSP.

So basically, an integer overflow causes the whole mess. I wish I could say that I was shocked, but here we are.

> an integer overflow

Yes but I'm not sure that's the point. I see that point being, "a subtraction between hashes was used instead of a comparison". "Hash of value "a lot" minus minus-a-lot" overflows.

And a nonsensical behaviour of the other product created a large number of those hashes... Which represent PhoneAccounts objects. The software that triggered the bug created a new PhoneAccounts at every onResume (or similar)...

Actually it was in Application.onCreate

https://katb.in/isiragorucu

Really feels like it’s more of a Google bug than Teams