[GH-ISSUE #125] Bug: stopping listen server #61

Closed
opened 2026-02-27 15:48:33 +03:00 by kerem · 6 comments
Owner

Originally created by @ghost on GitHub (May 12, 2015).
Original GitHub issue: https://github.com/quasar/Quasar/issues/125

Stopping the listen server with multiple clients connected will not correctly disconnect the client/remove from listview

Originally created by @ghost on GitHub (May 12, 2015). Original GitHub issue: https://github.com/quasar/Quasar/issues/125 Stopping the listen server with multiple clients connected will not correctly disconnect the client/remove from listview
kerem 2026-02-27 15:48:33 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@yankejustin commented on GitHub (May 12, 2015):

Will it remove the clients correctly and just not update the interface as it should, or is it not disconnecting them correctly entirely?

<!-- gh-comment-id:101347562 --> @yankejustin commented on GitHub (May 12, 2015): Will it remove the clients correctly and just not update the interface as it should, or is it not disconnecting them correctly entirely?
Author
Owner

@ghost commented on GitHub (May 12, 2015):

Both

<!-- gh-comment-id:101347713 --> @ghost commented on GitHub (May 12, 2015): Both
Author
Owner

@yankejustin commented on GitHub (May 12, 2015):

lol... got it! I will look into it.

<!-- gh-comment-id:101347805 --> @yankejustin commented on GitHub (May 12, 2015): lol... got it! I will look into it.
Author
Owner

@ghost commented on GitHub (May 12, 2015):

I didn't get a chance to debug it, but stopping the listen server, one of the clients would still be in the listview, and would respond to commands. It appeared that only one of the clients would hang left over. I tested this first with 2 active clients, then 3 active clients

<!-- gh-comment-id:101350333 --> @ghost commented on GitHub (May 12, 2015): I didn't get a chance to debug it, but stopping the listen server, one of the clients would still be in the listview, and would respond to commands. It appeared that only one of the clients would hang left over. I tested this first with 2 active clients, then 3 active clients
Author
Owner

@yankejustin commented on GitHub (May 12, 2015):

Interesting. Any exceptions thrown?

<!-- gh-comment-id:101350559 --> @yankejustin commented on GitHub (May 12, 2015): Interesting. Any exceptions thrown?
Author
Owner

@ghost commented on GitHub (May 12, 2015):

I believe so yes. Set a breakpoint on Disconnect method in xServer.Core.Server. I believe the problem lies within the logic in that method, although I'm not sure

<!-- gh-comment-id:101359917 --> @ghost commented on GitHub (May 12, 2015): I believe so yes. Set a breakpoint on Disconnect method in xServer.Core.Server. I believe the problem lies within the logic in that method, although I'm not sure
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Quasar#61
No description provided.