mirror of
https://github.com/nodejs/node.git
synced 2025-05-03 11:41:22 +00:00
6858c7e3e7
We clear the async id stack inside the uncaught exception handler and emit `after` events in the process, so we should not emit `after` a second time from the `runInAsyncScope()` code. This should match the behaviour we have in C++. Fixes: https://github.com/nodejs/node/issues/30080 PR-URL: https://github.com/nodejs/node/pull/30087 Reviewed-By: Gus Caplan <me@gus.host> Reviewed-By: Anto Aravinth <anto.aravinth.cse@gmail.com>
37 lines
920 B
JavaScript
37 lines
920 B
JavaScript
'use strict';
|
|
const common = require('../common');
|
|
const assert = require('assert');
|
|
const async_hooks = require('async_hooks');
|
|
|
|
// Regression test for https://github.com/nodejs/node/issues/30080:
|
|
// An uncaught exception inside a queueMicrotask callback should not lead
|
|
// to multiple after() calls for it.
|
|
|
|
let µtaskId;
|
|
const events = [];
|
|
|
|
async_hooks.createHook({
|
|
init(id, type, triggerId, resoure) {
|
|
if (type === 'Microtask') {
|
|
µtaskId = id;
|
|
events.push('init');
|
|
}
|
|
},
|
|
before(id) {
|
|
if (id === µtaskId) events.push('before');
|
|
},
|
|
after(id) {
|
|
if (id === µtaskId) events.push('after');
|
|
},
|
|
destroy(id) {
|
|
if (id === µtaskId) events.push('destroy');
|
|
}
|
|
}).enable();
|
|
|
|
queueMicrotask(() => { throw new Error(); });
|
|
|
|
process.on('uncaughtException', common.mustCall());
|
|
process.on('exit', () => {
|
|
assert.deepStrictEqual(events, ['init', 'after', 'before', 'destroy']);
|
|
});
|