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
Currently, on Android, Kable spins up a dedicated thread for I/O per peripheral. The thread is not spun down until the peripherals scope is cancelled.
This is not intuitive for consumers. Instead, the thread should be spun down on disconnect (or released back to a pool). This will remove the requirement to dispose of the peripheral scope in order to prevent leaking threads.
The text was updated successfully, but these errors were encountered:
Currently, on Android, Kable spins up a dedicated thread for I/O per peripheral. The thread is not spun down until the peripherals scope is cancelled.
This is not intuitive for consumers. Instead, the thread should be spun down on disconnect (or released back to a pool). This will remove the requirement to dispose of the peripheral scope in order to prevent leaking threads.
The text was updated successfully, but these errors were encountered: