Commit Graph

5 Commits

Author SHA1 Message Date
vadimt
ab469ac515 Better diagnosing leaked activities.
Test: manual
Bug: 181356264
Change-Id: I9bf843a1d26bc4cf255c1b8d2cce0febeaa4c4fe
2021-02-26 14:45:10 -08:00
vadimt
a190dc1f40 Zero tolerance towards referred destroyed activities
After a framework fix, we are not allowing rooted
destroyed activities at all.

Bug: 139137636

Change-Id: I0dda200db438e1a1b5587636ee08f65300dfa6d1
2020-06-26 18:33:27 +00:00
vadimt
921f9fd254 Support for counting activity creations
Bug: 139137636
Change-Id: Ib999fd3c82eb2997662578ec35e1d9e1e75e3cbb
2020-04-27 12:41:26 -07:00
vadimt
0703464556 Checking that there are no more than 2 live activities at any moment
This is tightening the makeshift strictmode criteria.

Starting with this moment, we will know that there is
no memory growth during tests execution, which is a big deal.

Big: 139137636

Change-Id: I5edc84524463bd1736d727496ad0fc031bb9624c
2020-04-23 16:35:09 +00:00
vadimt
b3e8ae8230 Makeshift analog of Strictmode leak detector
Strictmode leak detector is still a goal, but we might not be able to
achieve it in R. Strictmode has several framework-side bugs that perhaps
hide Launcher-side strictmode violations, while the time to fix
everything is limited, and new leaks get introduced all the time.

For now, implementing a check that is slightly more relaxed than
Strictmode, but still ensures the absence of leaks. I’ll keep
eliminating Strictmode violations as well as keep strengthening the
makeshift checker conditions until we’ll be able to enable Strictmode in
continuous testing.

I’m disabling Strictmode checks for now so that they don’t generate
unnecessary hprof dumps, but leaving the code dealing with strictmode.

Bug: 139137636
Change-Id: Ib10136b0d4e9892f70a19cd052ae5a54cf0a4efb
2020-04-22 19:00:12 -07:00