summaryrefslogtreecommitdiff
path: root/test/parallel/test-async-wrap-pop-id-during-load.js
diff options
context:
space:
mode:
authorTrevor Norris <trev.norris@gmail.com>2017-09-22 01:49:49 -0600
committerTrevor Norris <trev.norris@gmail.com>2017-09-27 02:07:43 -0600
commit92d7e81b73ba09479a57039042d58112ae89cac7 (patch)
treeeb6b2286178907db913d4a5b45cefec35ca24098 /test/parallel/test-async-wrap-pop-id-during-load.js
parent8a6f376e36bc93db76f08f7863864fafdec90fea (diff)
downloadandroid-node-v8-92d7e81b73ba09479a57039042d58112ae89cac7.tar.gz
android-node-v8-92d7e81b73ba09479a57039042d58112ae89cac7.tar.bz2
android-node-v8-92d7e81b73ba09479a57039042d58112ae89cac7.zip
src: clear async id stack if bootstrap throws
If bootstrap throws and if ids are added to the async id stack and if the exception wasn't handled by the fatal exception handler then the AsyncCallbackScope destructor will cause the AsyncHooks::pop_ids() stack check to fail. Causing the application to crash. So clear the async id stack manually. This is only possible if the user: 1) manually calls MakeCallback() or 2) uses async await in the top level. Which will cause _tickCallback() to fire before bootstrap finishes executing. The following example shows how the application can fail due to exceeding the maximum call stack while using async await: async function fn() { fn(); throw new Error(); } (async function() { await fn(); })(); If this occurs during bootstrap then the application will pring the following warning a number of times then exit with a status of 0: (node:*) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: *): Error Here's the same recursive call done after enabling a new AsyncHook() the following will print instead of the above warning and exit with a non-zero code (currently it's 7 because of how node::FatalException assigns error codes based on where the failure happened): script.js:25 async function fn() { ^ RangeError: Maximum call stack size exceeded at <anonymous> at fn (script.js:25:18) at fn (script.js:26:3) .... This has to do with how Promises lazily enable PromiseHook if an AsyncHook() is enabled. Whether these need to be made uniform is outside the scope of this commit Fixes: https://github.com/nodejs/node/issues/15448 PR-URL: https://github.com/nodejs/node/pull/15553 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
Diffstat (limited to 'test/parallel/test-async-wrap-pop-id-during-load.js')
-rw-r--r--test/parallel/test-async-wrap-pop-id-during-load.js21
1 files changed, 21 insertions, 0 deletions
diff --git a/test/parallel/test-async-wrap-pop-id-during-load.js b/test/parallel/test-async-wrap-pop-id-during-load.js
new file mode 100644
index 0000000000..1017fc02a7
--- /dev/null
+++ b/test/parallel/test-async-wrap-pop-id-during-load.js
@@ -0,0 +1,21 @@
+'use strict';
+
+require('../common');
+
+if (process.argv[2] === 'async') {
+ async function fn() {
+ fn();
+ throw new Error();
+ }
+ (async function() { await fn(); })();
+ // While the above should error, just in case it dosn't the script shouldn't
+ // fork itself indefinitely so return early.
+ return;
+}
+
+const assert = require('assert');
+const { spawnSync } = require('child_process');
+
+const ret = spawnSync(process.execPath, [__filename, 'async']);
+assert.strictEqual(ret.status, 0);
+assert.ok(!/async.*hook/i.test(ret.stderr.toString('utf8', 0, 1024)));