Broaden suppressions of probably-intentional leaks in AppKit.

Broaden suppressions of probably-intentional leaks in AppKit.

This reappeared in
http://build.chromium.org/p/chromium.memory.fyi/builders/Chromium%20Mac%20%28valgrind%29%281%29/builds/25830,
but none of the CLs in that blamelist look likely.  It's probably a change in
test randomization and/or bot configuration.

BUG=105525, 257276, 340847
NOTRY=true

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=248846

[tapted, 2014-02-05 00:35:37]

lgtm

I think this is reasonable. An explanation for the "why it appears now" could
simply be the randomization in test sharding -- whichever test goes over this
first will seed the cache and get the blame, so it will just shift around as
tests are added/removed.

https://codereview.chromium.org/155333002/diff/1/tools/valgrind/memcheck/supp...
File tools/valgrind/memcheck/suppressions_mac.txt (right):

https://codereview.chromium.org/155333002/diff/1/tools/valgrind/memcheck/supp...
tools/valgrind/memcheck/suppressions_mac.txt:103: # run of each reboot.
Maybe a ~See also issues 340847, 257276, 105525 in the comment?

https://codereview.chromium.org/155333002/diff/1/tools/valgrind/memcheck/supp...
tools/valgrind/memcheck/suppressions_mac.txt:108: fun:ripc_DrawPath
Haven't done much with suppressions.. but it might be good to keep the
  fun:CGContextDrawPath	
  fun:CGContextStrokePath

bits

[Jeffrey Yasskin, 2014-02-05 00:45:44]

On 2014/02/05 00:35:37, tapted wrote:
> I think this is reasonable. An explanation for the "why it appears now" could
> simply be the randomization in test sharding -- whichever test goes over this
> first will seed the cache and get the blame, so it will just shift around as
> tests are added/removed.

And that fact that it went away again in
http://build.chromium.org/p/chromium.memory.fyi/builders/Chromium%20Mac%20%28...
supports the randomization idea. A different-looking failure came back in
http://build.chromium.org/p/chromium.memory.fyi/builders/Chromium%20Mac%20%28...,
so I may be adding some similar suppressions later, but I'll get this one in
first.

https://codereview.chromium.org/155333002/diff/1/tools/valgrind/memcheck/supp...
File tools/valgrind/memcheck/suppressions_mac.txt (right):

https://codereview.chromium.org/155333002/diff/1/tools/valgrind/memcheck/supp...
tools/valgrind/memcheck/suppressions_mac.txt:103: # run of each reboot.
On 2014/02/05 00:35:37, tapted wrote:
> Maybe a ~See also issues 340847, 257276, 105525 in the comment?

Done.

https://codereview.chromium.org/155333002/diff/1/tools/valgrind/memcheck/supp...
tools/valgrind/memcheck/suppressions_mac.txt:108: fun:ripc_DrawPath
On 2014/02/05 00:35:37, tapted wrote:
> Haven't done much with suppressions.. but it might be good to keep the
>   fun:CGContextDrawPath	
>   fun:CGContextStrokePath
> 
> bits

I can definitely keep CGContextDrawPath. The traces vary between
CGContextStrokePath and CGContextFillPath, so I have to drop that one.

[Jeffrey Yasskin, 2014-02-05 01:06:41]

The CQ bit was checked by jyasskin@chromium.org

[commit-bot: I haz the power, 2014-02-05 03:53:51]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/jyasskin@chromium.org/155333002/60001

[commit-bot: I haz the power, 2014-02-05 04:24:43]

Change committed as 248846