Home Original page

child_process: remove nextTick on IPC message by mscdex · Pull Request #13648 · nodejs/node

@mscdex added child_process

Issues and PRs related to the child_process subsystem.

performance

Issues and PRs related to the performance of Node.js.

labels

Jun 13, 2017

@mscdex

cjihrig added a commit to cjihrig/node that referenced this pull request

Jun 24, 2017 
This commit fixes a regression related to IPC 'message'
events. When messages are not emitted in the next tick,
a 'message' handler that throws can break the IPC read
loop.

Refs: nodejs#6909
Refs: nodejs#13459
Refs: nodejs#13648
PR-URL: nodejs#13856
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>

addaleax pushed a commit that referenced this pull request

Jun 29, 2017 
This commit fixes a regression related to IPC 'message'
events. When messages are not emitted in the next tick,
a 'message' handler that throws can break the IPC read
loop.

Refs: #6909
Refs: #13459
Refs: #13648
PR-URL: #13856
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>

@mscdex mscdex deleted the child_process-no-nexttick-on-ipc-message branch

July 5, 2017 06:00

addaleax pushed a commit that referenced this pull request

Jul 11, 2017 
This commit fixes a regression related to IPC 'message'
events. When messages are not emitted in the next tick,
a 'message' handler that throws can break the IPC read
loop.

Refs: #6909
Refs: #13459
Refs: #13648
PR-URL: #13856
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>

addaleax pushed a commit that referenced this pull request

Jul 18, 2017 
This commit fixes a regression related to IPC 'message'
events. When messages are not emitted in the next tick,
a 'message' handler that throws can break the IPC read
loop.

Refs: #6909
Refs: #13459
Refs: #13648
PR-URL: #13856
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>