help icon indicating copy to clipboard operation
help copied to clipboard

Node version 18.0.0 crashes, when <audio src="..."></audio> is provided

Open neverlose-lv opened this issue 2 years ago • 2 comments

Version

18.0.0

Platform

Darwin Apples-MacBook-Pro.local 21.4.0 Darwin Kernel Version 21.4.0: Fri Mar 18 00:45:05 PDT 2022; root:xnu-8020.101.4~15/RELEASE_X86_64 x86_64

Subsystem

No response

What steps will reproduce the bug?

Fresh install of the latest Angular project.

Then replace the generated demo page with the source

<audio controls src="assets/sounds/click.ogg"></audio> (the file was added at this path)

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

all the time

What is the expected behavior?

not to crash.

What do you see instead?

node:events:505
      throw er; // Unhandled 'error' event
      ^

TypeError: Cannot set property closed of #<Readable> which has only a getter
    at FsReadStream.close (/Users/apower/Desktop/VR_Tours/node_modules/memfs/lib/volume.js:2047:17)
    at FsReadStream._destroy (/Users/apower/Desktop/VR_Tours/node_modules/memfs/lib/volume.js:2032:10)
    at _destroy (node:internal/streams/destroy:109:10)
    at class_1.destroy (node:internal/streams/destroy:71:5)
    at class_1.<anonymous> (/Users/apower/Desktop/VR_Tours/node_modules/memfs/lib/volume.js:1962:22)
    at class_1.emit (node:events:539:35)
    at endReadableNT (node:internal/streams/readable:1344:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on class_1 instance at:
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Node.js v18.0.0

Additional information

The 18.0.0 version is installed by the brew. Now downgraded to the 16th node version. The 16th node version works well.

neverlose-lv avatar May 10 '22 18:05 neverlose-lv

Also seeing this on 18.1.0. Any audio tag causes it to crash.

KevinHodder avatar May 13 '22 10:05 KevinHodder

Still getting the same crash on v18.7.0

racocvr avatar Aug 14 '22 06:08 racocvr

I don't suppose anyone has resolved this?

tomdmason avatar Dec 15 '22 20:12 tomdmason

Still seeing this on node:18.15.0 react:18.2.0

Found that updating memfs solved the issue.

littletuna4 avatar Jul 25 '23 00:07 littletuna4

@neverlose-lv did the suggestion from @littletuna4 solved your issue?

preveen-stack avatar Aug 25 '23 09:08 preveen-stack

It seems there has been no activity on this issue for a while, and it is being closed in 30 days. If you believe this issue should remain open, please leave a comment. If you need further assistance or have questions, you can also search for similar issues on Stack Overflow. Make sure to look at the README file for the most updated links.

github-actions[bot] avatar May 08 '24 01:05 github-actions[bot]

It seems there has been no activity on this issue for a while, and it is being closed. If you believe this issue should remain open, please leave a comment. If you need further assistance or have questions, you can also search for similar issues on Stack Overflow. Make sure to look at the README file for the most updated links.

github-actions[bot] avatar Jun 07 '24 01:06 github-actions[bot]