From c2f620ab76c3e42fa1fcdfde82aba7bcba3031e9 Mon Sep 17 00:00:00 2001 From: Anna Henningsen Date: Sun, 24 Feb 2019 21:52:14 +0100 Subject: src: refactor `Environment::GetCurrent(isolate)` usage Do not require an explicit `HandleScope`, or the ability to create one, when using `Environment::GetCurrent()`. `isolate->InContext()` is used as an indicator that it is probably okay to create a `HandleScope`, see also the short discussion in https://github.com/nodejs/node/pull/25775#pullrequestreview-197371049. PR-URL: https://github.com/nodejs/node/pull/26376 Reviewed-By: Gireesh Punathil Reviewed-By: Ben Noordhuis Reviewed-By: Colin Ihrig Reviewed-By: James M Snell --- src/node_errors.cc | 1 - 1 file changed, 1 deletion(-) (limited to 'src/node_errors.cc') diff --git a/src/node_errors.cc b/src/node_errors.cc index 1c15b55584..5c1e227966 100644 --- a/src/node_errors.cc +++ b/src/node_errors.cc @@ -314,7 +314,6 @@ void OnFatalError(const char* location, const char* message) { } #ifdef NODE_REPORT Isolate* isolate = Isolate::GetCurrent(); - HandleScope handle_scope(isolate); Environment* env = Environment::GetCurrent(isolate); if (env == nullptr || env->isolate_data()->options()->report_on_fatalerror) { report::TriggerNodeReport( -- cgit v1.2.1