Retire unused memcheck suppressions

Retire unused memcheck suppressions

Retire from tools/valgrind/memcheck/suppressions.txt any bug suppressions
that we have no known occurrences for in
http://chromium-build-logs.appspot.com/suppression_query

NOTRY=true
BUG=329389, 16326, 17291, 19196, 20997, 22098, 22923, 27837, 30346, 30633, 31985, 32273, 32624, 42842, 42942, 47950, 49279, 50968, 51153, 51379, 51590, 51679, 52837, 52957, 54308, 55533, 56359, 56676, 58321, 58340, 58546, 58561, 58574, 60556, 60654, 64887, 66853, 67142, 67261, 67553, 68553, 71728, 72544, 73415, 73675, 75019, 76197, 80537, 80551, 81796, 83609, 84224, 84265, 84770, 86481, 87423, 88640, 89942, 90057, 90215, 90240, 90487, 90496, 90671, 92741, 93250, 93730, 94764, 95448, 100982, 101750, 102327, 104447, 105744, 107696, 123307, 124488, 124496, 124500, 125692, 127716, 130362, 130449, 130619, 138060, 138712, 145650, 145693, 145695, 145696, 145697, 145699, 145708, 145712, 145723, 145735, 146464, 146950, 163922, 163924, 164176, 164178, 164179, 166818, 166819, 167175, 172005, 176619, 176621, 176889, 177213, 179758, 222876, 225028, 226254, 227278, 234845, 235584, 236791, 241932, 251034, 252036, 258132, 258466, 259357, 259789, 268267, 269844, 272596, 273398, 288804, 290559, 293058, 301900
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=241515

[Lei Zhang, 2013-12-18 05:42:16]

1) Can you put the bugs affected in the BUG= line?
2) You'll want NOTRY=true

lgtm

+groby, tomorrow's sheriff

[commit-bot: I haz the power, 2013-12-18 06:45:53]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/ericwilligers@chromium.org/111443009/1

[commit-bot: I haz the power, 2013-12-18 06:46:11]

Change committed as 241515

[Eric Willigers, 2013-12-18 07:56:00]

A revert of this CL has been created in
https://codereview.chromium.org/118073002/ by ericwilligers@chromium.org.

The reason for reverting is: Memory failures reported on bots.

[Peter Kasting, 2014-07-02 18:16:29]

Someone closing another bug pointed me at this CL.  Was this ever relanded
(partially or fully)?  It seems like this is something we want to land, and then
if necessary file or reopen bugs for failures that then pop up.

[Eric Willigers, 2014-07-03 03:37:17]

On 2014/07/02 18:16:29, Peter Kasting wrote:
> Someone closing another bug pointed me at this CL.  Was this ever relanded
> (partially or fully)?  It seems like this is something we want to land, and
then
> if necessary file or reopen bugs for failures that then pop up.

No, it wasn't relanded. We could either split it into about a hundred individual
CLs, but that would needlessly strain the commit queue. I would like to split it
into about 10 CLs, and land them progressively. This way, it is easier to
respond to failures.

[Peter Kasting, 2014-07-03 04:56:57]

On 2014/07/03 03:37:17, Eric Willigers wrote:
> On 2014/07/02 18:16:29, Peter Kasting wrote:
> > Someone closing another bug pointed me at this CL.  Was this ever relanded
> > (partially or fully)?  It seems like this is something we want to land, and
> then
> > if necessary file or reopen bugs for failures that then pop up.
> 
> No, it wasn't relanded. We could either split it into about a hundred
individual
> CLs, but that would needlessly strain the commit queue. I would like to split
it
> into about 10 CLs, and land them progressively. This way, it is easier to
> respond to failures.

OK.  Is there a bug tracking this?  I want to make sure this work actually gets
done :)

[Eric Willigers, 2014-07-07 01:28:26]

> OK.  Is there a bug tracking this?  I want to make sure this work actually
gets
> done :)

I have created bug https://code.google.com/p/chromium/issues/detail?id=391631