I think we should fix that anyway. If a timeout occurs where we do not exspect it, the following happens:

- The next size read returns a random size.
- If the buffer cannot be allocated, we read the remaining bytes from stream into null pointer.
- If the buffer can be allocated, it will be very large, screwing VM.
- The remaining bytes are read, and because size is much larger than what can be read, it will timeout in any case.
- A timeout after 1 - 5 seconds (user setting) leads to loss of frames, the live stream is broken.
- The stream will be reconnected.
- If we wrote to null pointer buffer, we will crash.

I consider this as a bug.