-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reproductible ERR_INTERNAL_ASSERTION on node 15 #38189
Labels
Comments
Can reproduce on master. Also happens when using |
The assert was added here: #35067 I think that there might be two issues here:
|
A reproduction without using pipeline: const { Writable } = require('stream');
// Create a dummy writable stream with backpressure
const writable = new Writable({
objectMode: true,
write: (chunk, encoding, callback) => {
setTimeout(callback, 100); // Backpressure
}
});
writable.write('a');
writable.write('b');
writable.destroy();
writable.destroy(); |
cc: @nodejs/streams @ronag |
I'll take a look. |
ronag
added a commit
to nxtedition/node
that referenced
this issue
Apr 12, 2021
Calling Writable.destroy() multiple times in the same tick could cause an assertion error. Fixes: nodejs#38189
ronag
added a commit
to nxtedition/node
that referenced
this issue
Apr 12, 2021
Calling Writable.destroy() multiple times in the same tick could cause an assertion error. Fixes: nodejs#38189
ronag
added a commit
to nxtedition/node
that referenced
this issue
Apr 29, 2021
Calling Writable.destroy() multiple times in the same tick could cause an assertion error. Fixes: nodejs#38189 PR-URL: nodejs#38221 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Nitzan Uziely <[email protected]> Reviewed-By: Rich Trott <[email protected]>
ronag
added a commit
to nxtedition/node
that referenced
this issue
Apr 29, 2021
Calling Writable.destroy() multiple times in the same tick could cause an assertion error. Fixes: nodejs#38189 PR-URL: nodejs#38221 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Nitzan Uziely <[email protected]> Reviewed-By: Rich Trott <[email protected]>
ronag
added a commit
to nxtedition/node
that referenced
this issue
Apr 29, 2021
Calling Writable.destroy() multiple times in the same tick could cause an assertion error. Fixes: nodejs#38189 PR-URL: nodejs#38221 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Nitzan Uziely <[email protected]> Reviewed-By: Rich Trott <[email protected]> Backport-PR-URL: nodejs#38473
ronag
added a commit
to nxtedition/node
that referenced
this issue
Apr 29, 2021
Calling Writable.destroy() multiple times in the same tick could cause an assertion error. Fixes: nodejs#38189 PR-URL: nodejs#38221 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Nitzan Uziely <[email protected]> Reviewed-By: Rich Trott <[email protected]> Backport-PR-URL: nodejs#38473
ronag
added a commit
to nxtedition/node
that referenced
this issue
Apr 29, 2021
Calling Writable.destroy() multiple times in the same tick could cause an assertion error. Fixes: nodejs#38189 PR-URL: nodejs#38221 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Nitzan Uziely <[email protected]> Reviewed-By: Rich Trott <[email protected]> Backport-PR-URL: nodejs#38473
targos
pushed a commit
that referenced
this issue
May 30, 2021
Calling Writable.destroy() multiple times in the same tick could cause an assertion error. Fixes: #38189 PR-URL: #38221 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Nitzan Uziely <[email protected]> Reviewed-By: Rich Trott <[email protected]> Backport-PR-URL: #38473
targos
pushed a commit
that referenced
this issue
Jun 5, 2021
Calling Writable.destroy() multiple times in the same tick could cause an assertion error. Fixes: #38189 PR-URL: #38221 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Nitzan Uziely <[email protected]> Reviewed-By: Rich Trott <[email protected]> Backport-PR-URL: #38473
targos
pushed a commit
that referenced
this issue
Jun 5, 2021
Calling Writable.destroy() multiple times in the same tick could cause an assertion error. Fixes: #38189 PR-URL: #38221 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Nitzan Uziely <[email protected]> Reviewed-By: Rich Trott <[email protected]> Backport-PR-URL: #38473
targos
pushed a commit
that referenced
this issue
Jun 11, 2021
Calling Writable.destroy() multiple times in the same tick could cause an assertion error. Fixes: #38189 PR-URL: #38221 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Nitzan Uziely <[email protected]> Reviewed-By: Rich Trott <[email protected]> Backport-PR-URL: #38473
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What steps will reproduce the bug?
I had a ERR_INTERNAL_ASSERTION when trying to run our application using node 15.x, for a stream destroy test. This code is the minimal version to reproduce it.
The code works ok on node 14.16.1, but fails under node 15.14.0
To reproduce (under node 15):
Expected behavior (under node14):
The text was updated successfully, but these errors were encountered: