Remove likely stale drmemory suppressions.

Remove likely stale drmemory suppressions.

The corresponding valgrind suppressions have long since been removed, so match
the drmemory side. If they appear again, we should file new bugs and
investigate anew.

BUG=117427, 79933
Committed: https://crrev.com/3a8ebb01ce21bd1d7f58a17ad2f6d4b9f9bdeff2
Cr-Commit-Position: refs/heads/master@{#333108}

[davidben, 2015-06-05 18:52:49]

davidben@chromium.org changed reviewers:
+ mmenke@chromium.org

[davidben, 2015-06-05 18:52:49]

I think we should just spring-clean here. It's not worth the time to dig into
whether it's still there.

[mmenke, 2015-06-05 18:54:37]

On 2015/06/05 18:52:49, David Benjamin wrote:
> I think we should just spring-clean here. It's not worth the time to dig into
> whether it's still there.

SGTM.  LGTM.  GWBSQBL.

[davidben, 2015-06-05 19:32:33]

Hrmf. Of all the try bots, the one to get stuck was the only one I cared about
(win_drmemory). Whatever, I'll CQ this and we'll see what happens.

[davidben, 2015-06-05 19:32:38]

The CQ bit was checked by davidben@chromium.org

[commit-bot: I haz the power, 2015-06-05 19:34:41]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1151883005/1

[commit-bot: I haz the power, 2015-06-05 19:39:34]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-06-05 20:00:10]

Patchset 1 (id:??) landed as
https://crrev.com/3a8ebb01ce21bd1d7f58a17ad2f6d4b9f9bdeff2
Cr-Commit-Position: refs/heads/master@{#333108}