Do not leak message object beyond try-catch.

Do not leak message object beyond try-catch.

R=mstarzinger@chromium.org

Committed: https://crrev.com/14eba9b27531911f8466a5877fc66b64bc98bdb6
Cr-Commit-Position: refs/heads/master@{#28612}

[Yang, 2015-05-22 11:55:45]

The CQ bit was checked by yangguo@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-05-22 11:56:01]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1150293002/20001

[commit-bot: I haz the power, 2015-05-22 12:24:55]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-05-22 12:24:57]

Dry run: Try jobs failed on following builders:
  v8_linux64_asan_rel on tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux64_asan_rel/builds/...)

[Yang, 2015-05-22 12:45:46]

The CQ bit was checked by yangguo@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-05-22 12:46:15]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1150293002/20001

[Michael Starzinger, 2015-05-22 13:02:29]

LGTM. I am fine with addressing the comment in a follow-up CL.

https://codereview.chromium.org/1150293002/diff/20001/src/full-codegen.h
File src/full-codegen.h (right):

https://codereview.chromium.org/1150293002/diff/20001/src/full-codegen.h#newc...
src/full-codegen.h:712: void EnterCatchBlock();
nit: If we extend this to the "try-finally" statement as well, then it might
make sense to rename the function to ClearMessageObject() or similar instead.

https://codereview.chromium.org/1150293002/diff/20001/test/cctest/test-heap.cc
File test/cctest/test-heap.cc (right):

https://codereview.chromium.org/1150293002/diff/20001/test/cctest/test-heap.c...
test/cctest/test-heap.cc:5583: "  throw 'message';"
As discussed offline: We should have the same problem with a finally block.
Correct? Consider the following example:

try {
  throw 'message';
} finally {
  break;
}

[commit-bot: I haz the power, 2015-05-22 13:55:48]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-05-22 13:55:49]

Dry run: Try jobs failed on following builders:
  v8_linux64_asan_rel on tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux64_asan_rel/builds/...)

[Yang, 2015-05-26 07:18:54]

The CQ bit was checked by yangguo@chromium.org

[Yang, 2015-05-26 07:18:54]

The patchset sent to the CQ was uploaded after l-g-t-m from
mstarzinger@chromium.org
Link to the patchset: https://codereview.chromium.org/1150293002/#ps60001
(title: "fix memory leak by setting flag")

[commit-bot: I haz the power, 2015-05-26 07:19:05]

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

[commit-bot: I haz the power, 2015-05-26 08:00:11]

Committed patchset #4 (id:60001)

[commit-bot: I haz the power, 2015-05-26 08:00:28]

Patchset 4 (id:??) landed as
https://crrev.com/14eba9b27531911f8466a5877fc66b64bc98bdb6
Cr-Commit-Position: refs/heads/master@{#28612}