Bot unexcepted disconnect about ts3j HOT 4 CLOSED

The full output here will be very helpful to diagnose the issue here, thank-you for putting this together. I'll take a look as soon as I can.

from ts3j.

Given:

if (size > 65536) throw new IllegalArgumentException("decompression too large: " + size);

It really doesn't look like there is any repercussion to us removing or changing this check, aside from the fact that we do need to be aware of opening up the potential for DoS attacks if someone injects a decompression request that is far too large for the heap.

from ts3j.

Best option is to are this value as client parameter in api

from ts3j.

This should be fixed, now, with two separate constraints on decompressed packet sizes.

from ts3j.