reland 1: Add basic memory usage tests for attachment brokering.

reland 1: Add basic memory usage tests for attachment brokering.

One of the assumptions of the newly added tests was violated under a sanitizer
build. This is not particularly surprising, so I disabled that check for
sanitizer builds.

> I added two tests for memory leaks in the attachment brokering process. The
> first checks memory usage after brokering a single, large, shared memory object.
> The second checks memory usage after brokering a thousand, smaller memory
> objects.
>
> BUG=557387
> Committed: https://crrev.com/a519e56d03e1f6d69b7475bdd006f5e47b4f581e
> Cr-Commit-Position: refs/heads/master@{#360935}

BUG=557387
Committed: https://crrev.com/e50acd8893ed6898bc5767ae6fd9859493be3a0d
Cr-Commit-Position: refs/heads/master@{#361391}

[erikchen, 2015-11-23 19:16:31]

erikchen@chromium.org changed reviewers:
+ tsepez@chromium.org

[erikchen, 2015-11-23 19:16:31]

tsepez: Please review.

Diff patch set 3 against patch set 1 to see changes from the landed CL.

[Tom Sepez, 2015-11-23 20:28:20]

Howabout just changing the shm read to a write?  That would avoid the uninit
warning.

[erikchen, 2015-11-23 22:16:50]

On 2015/11/23 20:28:20, Tom Sepez wrote:
> Howabout just changing the shm read to a write?  That would avoid the uninit
> warning.

good point - done.

[Tom Sepez, 2015-11-24 17:13:07]

lgtm

[erikchen, 2015-11-24 18:01:05]

The CQ bit was checked by erikchen@chromium.org

[commit-bot: I haz the power, 2015-11-24 18:03:44]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1464413002/80001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1464413002/80001

[commit-bot: I haz the power, 2015-11-24 18:29:05]

Committed patchset #5 (id:80001)

[commit-bot: I haz the power, 2015-11-24 18:29:53]

Patchset 5 (id:??) landed as
https://crrev.com/e50acd8893ed6898bc5767ae6fd9859493be3a0d
Cr-Commit-Position: refs/heads/master@{#361391}