You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When disconnecting from a TDK there is always a StreamPacketizer thread that remains running in the app and eating the CPU.
The run loop in the StreamPacketizer keeps reading from the InputStream and returns -1, it never exits.
I have traced the problem down to the audio stream, once it is started, it does not get cleaned-up when the proxy session ends.
Calling endPCM() in onProxyClosed does not work, it just returns false because the SdlSession object is different than the one used to start the audio stream.
As it is right now there is no elegant way to stop an audio stream when connecting/disconnecting to the
TDK without the StreamPacketizer thread hanging.
100% Reproducible on SDL 4.3 and 4.4. Tried with various devices.
The text was updated successfully, but these errors were encountered:
When disconnecting from a TDK there is always a StreamPacketizer thread that remains running in the app and eating the CPU.
The run loop in the StreamPacketizer keeps reading from the InputStream and returns -1, it never exits.
I have traced the problem down to the audio stream, once it is started, it does not get cleaned-up when the proxy session ends.
Calling endPCM() in onProxyClosed does not work, it just returns false because the SdlSession object is different than the one used to start the audio stream.
As it is right now there is no elegant way to stop an audio stream when connecting/disconnecting to the
TDK without the StreamPacketizer thread hanging.
100% Reproducible on SDL 4.3 and 4.4. Tried with various devices.
The text was updated successfully, but these errors were encountered: