suppress memory leak from ShellBrowserMainParts::PreMainMessageLoopRun

suppress memory leak from ShellBrowserMainParts::PreMainMessageLoopRun 
TBR=nileshagrawal@chromium.org 
BUG=246359
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=203779

[zhaoqin, 2013-06-03 21:40:14]

Committed patchset #1 manually as r203779 (presubmit successful).

[jam, 2013-06-03 21:58:04]

this call stack is too generic, it will basically cover all allocations during
content_browsertests.

[zhaoqin, 2013-06-03 22:18:10]

On 2013/06/03 21:58:04, jam wrote:
> this call stack is too generic, it will basically cover all allocations during
> content_browsertests.

that's the full call stack I got without any cut.

[jam, 2013-06-04 00:36:01]

On 2013/06/03 22:18:10, zhaoqin wrote:
> On 2013/06/03 21:58:04, jam wrote:
> > this call stack is too generic, it will basically cover all allocations
during
> > content_browsertests.
> 
> that's the full call stack I got without any cut.

what I'm trying to say is there's no point adding that callstack. running in
content_browsertests now won't find any leaks.

i'd try to find a more specific callstack, I don't know why you only got that
stack that time. Do other runs provide better callstacks?

[jam, 2013-06-04 16:21:27]

ping

[zhaoqin, 2013-06-04 18:32:16]

On 2013/06/04 16:21:27, jam wrote:
> ping

it only suppresses the memory leaks that allocated from PreMainMessageLoopRun,
so should be fine.