test: keep cif structs alive during gc #380
Closed
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.
Up until now, test/callback.js assumed that the
cb.cif
objectwould not be garbage collected and was available to
Callback::Invoke
.That has never been a valid assumption, but as of
nodejs/node#12141 Buffers created with
new Buffer(n)
each have their ownArrayBuffer
which getsgarbage-collected much more easily, which in turn would
crash the test suite here.
To (lazy-)fix this, assign
cb._cif
to some global variable that isguaranteed to stay alive.