WebSocket: message handler sometimes called with null data (potentially issue in frame processing)

[farwayer]

Bug Description

I’ll say right away that the bug is floating and I don’t have a ready-made recipe for reproducing it. The bug usually appeared during debugging. Apparently, timings and the sequence of data arrival are important. The server should also send pings to get this effect.

From the screenshot you can see that the websocketMessageReceived function is called with this.#info.originalOpcode=9 (PING frame type), which should not happen.

Logs & Screenshots

Environment

node v21.6.2