🔄 WebSocket sends corrupted characters after idle period with no messages

Description

After connecting successfully to the WebSocket server, the client (yaak.app) occasionally displays corrupted or unreadable characters in the message log when no messages have been received for some time.

The connection remains open (CONNECTED status is still shown), but random sequences of unreadable symbols such as B��1 or 澪� appear in the output.
No actual data is being transmitted from the server during those intervals.

Expected Behavior

• The WebSocket client should remain idle without displaying any messages until a valid frame is received.

• No garbled or corrupted characters should appear when no actual data is sent by the server.

Actual Behavior

• After several seconds or minutes of inactivity, unexpected unreadable characters are displayed in the message log.

• These messages do not correspond to any real data sent from the backend.

Steps to Reproduce

1. Connect to the WebSocket server (using yaak.app).

2. Wait for a few minutes without sending or receiving any messages.

3. Observe the message log — corrupted or unreadable characters appear unexpectedly.