According to Chrome's serial documentation, when onReceiveError is called the connection is only paused but not automatically closed. This fixes an edge case where the connectionId was being reset but the underlying connection was never closed, leading to a connection leak.
According to Chrome's serial documentation, when
onReceiveErroris called the connection is only paused but not automatically closed. This fixes an edge case where theconnectionIdwas being reset but the underlying connection was never closed, leading to a connection leak.