One area to investigate: It appears we keep a map of iconUrl -> Bitmap which does not get cleared until Chrome is killed.

As we move to support larger icons, this may prove a problem.

mmocny@, that's in NearbyUrlsAdapter, which is tied to the ListUrlsActivity.  It clears whenever the Activity is removed from memory.

I was talking with @agrieve and he mentioned that the UMA reports often have noise, so this is likely just an anomaly.  There are other automated scans on memory impact, and if no one has spoken up, its likely we haven't done anything noticeable.

That said, its also possible that this only happens with beacons around, and that our testers don't have any nearby.

I think a bit of due diligence will go a long way.  Andrew suggested a tool we can use to help understand memory usage, but I forgot what it was.

Was it MAT?  I've played with that some.

Things look good/as expected so far.  I'm going to mark this fixed unless we have other specific inquiries.

Deleted: pwheap.png 170 KB

	pwheap.png 170 KB View Download