Do not print stack-trace for OOM when GC is in progress.

Do not print stack-trace for OOM when GC is in progress.

BUG=chromium:553051
LOG=NO

Committed: https://crrev.com/d763c7d0899ea25f644ac738bb4f858457835e68
Cr-Commit-Position: refs/heads/master@{#31877}

[ulan, 2015-11-09 10:19:14]

ulan@chromium.org changed reviewers:
+ jarin@chromium.org

[ulan, 2015-11-09 10:19:15]

I decided to just disable stack traces for OOM in GC. We will still get stack
traces for other OOMs.

Is it ok to land without regression test since the test would crash both in
success (OOM) and failure (DCHECK) cases?

[Jarin, 2015-11-09 10:22:19]

lgtm. I think it is ok to omit regression test for the OOM case.

[ulan, 2015-11-09 10:28:49]

The CQ bit was checked by ulan@chromium.org

[commit-bot: I haz the power, 2015-11-09 10:28:58]

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

[commit-bot: I haz the power, 2015-11-09 11:06:45]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-11-09 11:07:12]

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