"zlib.createGzip()._transform" results in an abort

[zyscoder]

Version

v22.11.0

Platform

Linux u24vm 6.8.0-50-generic #51-Ubuntu SMP PREEMPT_DYNAMIC Sat Nov  9 17:58:29 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Subsystem

zlib

What steps will reproduce the bug?

Setup a node instance,

» node

and run the following javascript code.

zlib.createGzip()._transform("");

Then an abort occurs.

I reported a similar issue three years ago #37884.
Unfortunately, I found the problem is still there.
Feel free to close the two issues if you think the problem is not necessary to fix.

How often does it reproduce? Is there a required condition?

This abort can always be triggered following the steps above.

What is the expected behavior? Why is that the expected behavior?

If any error occurs, an exception or other similar error-reporting stuff should be thrown. There is no reason to abort the whole node process.

What do you see instead?

» node                                                                                                                                                                                    
Welcome to Node.js v22.11.0.
Type ".help" for more information.
> 
> zlib.createGzip()._transform("");

  #  node[1069309]: static void node::{anonymous}::CompressionStream<CompressionContext>::Write(const v8::FunctionCallbackInfo<v8::Value>&) [with bool async = true; CompressionContext = node::{anonymous}::ZlibContext] at ../src/node_zlib.cc:328
  #  Assertion failed: Buffer::HasInstance(args[1])

----- Native stack trace -----

 1: 0xf76527 node::Assert(node::AssertionInfo const&) [node]
 2: 0x10b223a  [node]
 3: 0x70e96bc0f5e2 

----- JavaScript stack trace -----

1: processChunk (node:zlib:491:10)
2: ZlibBase._transform (node:zlib:385:3)
3: REPL2:1:19
4: runInThisContext (node:vm:137:12)
5: defaultEval (node:repl:598:22)
6: bound (node:domain:433:15)
7: runBound (node:domain:444:12)
8: onLine (node:repl:927:10)
9: emit (node:events:530:35)
10: emit (node:domain:489:12)


[1]    1069309 IOT instruction (core dumped)  node

Additional information

No response

[marco-ippolito]

Closing as duplicate of #37884, please write on the other issue.