Repository navigation
received SIGSEGV on rejecting a promise #13782
Description
- Version:
v6.11.0 - Platform:
Linux 4.4.0-79-generic Revert "path: resolve normalize drive letter to lower case" #100-Ubuntu SMP Wed May 17 19:58:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Intel(R) Xeon(R) CPU E5-2666 v3 @ 2.90GHz
I encountered the problem on my app.
Fact:
The sources (1) and (5) occurs SIGSEGV
But (2), (3), (4) hasn't the problem.
Option:
--max_old_space_size=1024 --expose-gc
and the process is forked process by forever.
(*) catch( ... ) part is written only in (1).
(1)
var when = Promise.resolve();
when = when.then(function() {
return new Promise(function(rsl, rej) {
rej('THROW ERROR'); // => SIGSEGV
});
});
when['catch'](function(e){
console.log(e);
});(2)
var when = Promise.resolve();
when = when.then(function() {
return new Promise(function(rsl, rej) {
rsl(); // => OK
});
});(3)
var when = Promise.resolve();
when = when.then(function() {
return new Promise(function(rsl, rej) {
process.nextTick(rej); // => OK
});
});(4)
var when = Promise.resolve();
when = when.then(function() {
return new Promise(function(rsl, rej) {
setImmediate(rej); // => OK
});
});(5)
var when = Promise.resolve();
when = when.then(function() {
return new Promise(function(rsl, rej) {
throw 'THROW ERROR' // => SIGSEGV
});
});I wonder when this phenomena will reproduce in what condition.
Activity
bnoordhuis commentedon Jun 19, 2017
I can't reproduce locally. Can you turn on core dump (
ulimit -c unlimited) and check the backtrace (thebtcommand) in gdb? Does it happen for you with node 8?ystskm commentedon Jun 19, 2017
@bnoordhuis
Thx, that's a good idea!
Unfortunately, my app cannot running on v8.1.2 for the contextify module.
And I'm trying to get the backtrace without forever.
Then the backtrace is found.
Should get any more dump?
(Sorry for not familier with gdb dump)
bnoordhuis commentedon Jun 19, 2017
Thanks, that's helpful. Can you paste the output of
info registersanddisassemble?ystskm commentedon Jun 19, 2017
okay!
bnoordhuis commentedon Jun 19, 2017
Let me guess, those examples you posted are running inside a contextify context?
ystskm commentedon Jun 19, 2017
In fact, these codes are running on JSDOM.
Oh, that's a good hint!
I found the suspcious Segmentation fault!
(1-1) jsdom@3.1.1(my use)
(1-2) jsdom@3.1.1(my use)
(2-1) jsdom@6.5.1(checking module)
(2-2) jsdom@6.5.1(checking module)
Should think is contextify bug?
I know the logic is running on Node v0.12.10. with using es6-promise module.
bnoordhuis commentedon Jun 19, 2017
Yes, it's a contextify issue. Contexts created by node have a pointer to node's execution environment but contextify's contexts don't. The segfault you get is node trying to look up that pointer. Unfortunately, there is no way for node to check if a context has that pointer or not.
FWIW, you shouldn't need contextify with node 8 (and neither with node 6, I think), the built-in vm module should be able to do everything contextify does.
In fact, I thought jsdom was already using vm. Perhaps you are using an old version?
ystskm commentedon Jun 19, 2017
I understand the reason!
You are correct that the jsdom seems to be a little bit old for the new version of node.
I'll try to upgrade jsdom module. Thank you very much!
ADDITIONAL:
If you know, let me know why the error is not occured when with setImmediate.