When calling wsd:close-connection on a connection object, the websocket read thread associated with that object starts using 100% CPU trying to call READ-SEQUENCE, erroring out (because the stream is closed), and then for some reason it ignores the error and retries ad infinitum.
I worked around this with bt:destroy-thread in my application, but ideally the read thread should be properly closed when the connection is... (and, for that matter, probably shouldn't ignore read errors either)
When calling
wsd:close-connectionon a connection object, the websocket read thread associated with that object starts using 100% CPU trying to callREAD-SEQUENCE, erroring out (because the stream is closed), and then for some reason it ignores the error and retries ad infinitum.I worked around this with
bt:destroy-threadin my application, but ideally the read thread should be properly closed when the connection is... (and, for that matter, probably shouldn't ignore read errors either)