Fix PrettierAsync segmentation fault #138
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This pull request fixes #135 where the command
PrettierAsync
causes Vim to crash due to segmentation fault.The following is a summary of the involved fixes:
Transportation fix:
in_io
back to the default ofpipe
Performance fix:
Test Plan
Error Reproduction Steps:
crash.js
file from @nerfologist reproduction example - https://raw.githubusercontent.com/nerfologist/vim-prettier-async-segv-bug/master/crash.jscrash.js
in vimPrettierAsync
NOTE: If the seg fault doesn't occur, increase the number of lines calling
someFunc('something', () => {});
. Eventually you will reach your platforms magic buffer size to cause the seg fault.Test Steps For Fix:
crash.js
file from @nerfologist reproduction example - https://raw.githubusercontent.com/nerfologist/vim-prettier-async-segv-bug/master/crash.jscrash.js
in vimPrettierAsync