Desktop 7.18.0 random crashes when scrolling window

[jimwsmith]

Using a supported version?

• I have searched searched open and closed issues for duplicates.
• I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Overall summary

Running on Windows 10 (fully patched)
Previous Signal versions have been stable
Random when scrolling (not all the time I get this crash screen)
Signal closes, reopens (and usually) will run for a couple of minutes before crashing again

Unhandled Error

TypeError [ERR_INVALID_STATE]: Invalid state: Controller is already closed
at ReadableStreamDefaultController.close (node:internal/webstreams/readablestream:1065:13)
at ReadStream. (node:internal/webstreams/adapters:451:16)
at ReadStream. (node:internal/util:525:20)
at ReadStream.onclose (node:internal/streams/end-of-stream:162:14)
at ReadStream.emit (node:events:519:28)
at emitCloseNT (node:internal/streams/destroy:147:10)
at process.processTicksAndRejections (node:internal/process/task_queues:81:21)

Steps to reproduce

Go to any chat
Use mouse wheel to scroll list of chats in left hand pane
Sometimes, the crash occurs instantly, sometimes its OK for a few minutes

Expected result

Signal doesn't crash

Actual result

Signal crashes, displays error, then closes

Screenshots

No response

Signal version

7.18.0

Operating system

Windows 10

Version of Signal on your phone

7.21 (227)

Link to debug log

No response

[jimwsmith]

Note same crash behaviour on another laptop running Windows 11
Same Signal version 7.18.0

[MISTREATEDSOUL]

I am also facing the same issue because of this i have reinstalled my win 11 but it's the same.

Unhandled Error TypeError [ERR_INVALID_STATE]: Invalid state: Controller is already closed
at ReadableStreamDefaultController.close (node:internal/webstreams/readablestream:1065:13)
at ReadStream. (node:internal/webstreams/adapters:451:16)
at ReadStream. (node:internal/util:525:20)
at ReadStream.onclose (node:internal/streams/end-of-stream:162:14)
at ReadStream.emit (node:events:519:28)
at emitCloseNT (node:internal/streams/destroy:147:10)
at process.processTicksAndRejections (node:internal/process/task_queues:81:21)

[indutny-signal]

Hello! Sorry you ran into this issue, we have identified a bug in upstream code (Node.js) that could be causing this, and working on a fix and a temporary remedy.