From 002dacb7f7a909c42f0ce69bee5b58e9158b5630 Mon Sep 17 00:00:00 2001 From: Anna Henningsen Date: Mon, 15 Apr 2019 22:19:59 +0200 Subject: [PATCH] worker: handle exception when creating execArgv errors MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Handle possible JS exceptions that can occur by returning to JS land immediately. The motivation for this change is that `USE(….FromJust());` is an anti-pattern, and `.FromJust()` with an unused return value is superseded by `.Check()`. However, in this case, checking that the operation succeeded is not necessary. Refs: https://github.com/nodejs/node/pull/27162 PR-URL: https://github.com/nodejs/node/pull/27245 Reviewed-By: Ben Noordhuis Reviewed-By: James M Snell --- src/node_worker.cc | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/src/node_worker.cc b/src/node_worker.cc index bdf324fa047624..b9143eca7aafdd 100644 --- a/src/node_worker.cc +++ b/src/node_worker.cc @@ -459,13 +459,17 @@ void Worker::New(const FunctionCallbackInfo& args) { // The first argument is program name. invalid_args.erase(invalid_args.begin()); if (errors.size() > 0 || invalid_args.size() > 0) { - v8::Local error = - ToV8Value(env->context(), - errors.size() > 0 ? errors : invalid_args) - .ToLocalChecked(); + v8::Local error; + if (!ToV8Value(env->context(), + errors.size() > 0 ? errors : invalid_args) + .ToLocal(&error)) { + return; + } Local key = FIXED_ONE_BYTE_STRING(env->isolate(), "invalidExecArgv"); - USE(args.This()->Set(env->context(), key, error).FromJust()); + // Ignore the return value of Set() because exceptions bubble up to JS + // when we return anyway. + USE(args.This()->Set(env->context(), key, error)); return; } }