starred/Quasar

Fork 0

mirror of https://github.com/quasar/Quasar.git synced 2026-04-25 15:25:59 +03:00

[GH-ISSUE #830] Reducing "Remote Desktop" Window cause client to briefly disconnect #556

New issue

Closed

opened 2026-02-27 15:50:53 +03:00 by kerem · 8 comments

kerem commented

2026-02-27 15:50:53 +03:00

Owner

Originally created by @azsde on GitHub (Jun 10, 2020).
Original GitHub issue: https://github.com/quasar/Quasar/issues/830

When viewing a client's remote desktop, reducing the window (by pressing the "-" button), cause the client to disconnect.

Steps to reproduce the behavior:

Go to a connected client "Remote Desktop"
Click on 'Start'
Click on minimize button "-"
Client is disconnected

Expected behavior

The remote desktop should keep going when the window is minized and the client should not be disconnected.

Server OS: Windows 10
Client OS: Windows 10
Server installed .NET Framework version: 4.8.03752
Client installed .NET Framework version: 4.8.04084
Quasar Version: 1.4.0

Build configuration: master

Originally created by @azsde on GitHub (Jun 10, 2020). Original GitHub issue: https://github.com/quasar/Quasar/issues/830 When viewing a client's remote desktop, reducing the window (by pressing the "-" button), cause the client to disconnect. Steps to reproduce the behavior: 1. Go to a connected client "Remote Desktop" 2. Click on 'Start' 3. Click on minimize button "-" 4. Client is disconnected **Expected behavior** The remote desktop should keep going when the window is minized and the client should not be disconnected. Server OS: Windows 10 Client OS: Windows 10 Server installed .NET Framework version: 4.8.03752 Client installed .NET Framework version: 4.8.04084 Quasar Version: 1.4.0 Build configuration: master

kerem

2026-02-27 15:50:53 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-27 15:50:54 +03:00

Author

Owner

@ghost commented on GitHub (Jun 10, 2020):

you mean minimizing it? I'll look in the code to see what the click event does.

@ghost commented on GitHub (Jun 10, 2020): you mean minimizing it? I'll look in the code to see what the click event does.

kerem commented

2026-02-27 15:50:54 +03:00

Author

Owner

@azsde commented on GitHub (Jun 10, 2020):

Yes sorry, minimizing.

In french we use another word, sorry for the mix-up.

@azsde commented on GitHub (Jun 10, 2020): Yes sorry, minimizing. In french we use another word, sorry for the mix-up.

kerem commented

2026-02-27 15:50:54 +03:00

Author

Owner

@ghost commented on GitHub (Jun 10, 2020):

Yes sorry, minimizing.

In french we use another word, sorry for the mix-up.

No problem! I'm downloading the Quasar repository and will try to recreate the problem right now!

@ghost commented on GitHub (Jun 10, 2020): > Yes sorry, minimizing. > > In french we use another word, sorry for the mix-up. No problem! I'm downloading the Quasar repository and will try to recreate the problem right now!

kerem commented

2026-02-27 15:50:54 +03:00

Author

Owner

@ghost commented on GitHub (Jun 11, 2020):

I'm sorry I had to do something today but I'll make sure to respond in a couple hours or if I go to sleep when I wake up, sorry but it's 3 am right now.

@ghost commented on GitHub (Jun 11, 2020): I'm sorry I had to do something today but I'll make sure to respond in a couple hours or if I go to sleep when I wake up, sorry but it's 3 am right now.

kerem commented

2026-02-27 15:50:54 +03:00

Author

Owner

@azsde commented on GitHub (Jun 11, 2020):

I already provided those informations in the original post, I build Quasar myself based on the latest master commit.

@azsde commented on GitHub (Jun 11, 2020): I already provided those informations in the original post, I build Quasar myself based on the latest master commit.

kerem commented

2026-02-27 15:50:54 +03:00

Author

Owner

@ghost commented on GitHub (Jun 11, 2020):

I know that is why I deleted the comment, I forgot that you need to specify those.

But anyways, here's what I found:

I'm looking into it and I noticed quasar closes the connection when the async receiver gets an error.
Could maybe happen due to the client sending incorrect data that causes an error to happen, Still looking into it

@ghost commented on GitHub (Jun 11, 2020): I know that is why I deleted the comment, I forgot that you need to specify those. But anyways, here's what I found: I'm looking into it and I noticed quasar closes the connection when the async receiver gets an error. Could maybe happen due to the client sending incorrect data that causes an error to happen, Still looking into it

kerem commented

2026-02-27 15:50:54 +03:00

Author

Owner

@ghost commented on GitHub (Jun 11, 2020):

Update:

My 3 main reasons for it happening are

Client sending incorrect data that can't be parsed so server drops connection
Server sending unsafe data that drops the connection
The amount of data sent is over the 5 megabyte limit MaxXor put in place.

@ghost commented on GitHub (Jun 11, 2020): Update: My 3 main reasons for it happening are Client sending incorrect data that can't be parsed so server drops connection Server sending unsafe data that drops the connection The amount of data sent is over the 5 megabyte limit MaxXor put in place.

kerem commented

2026-02-27 15:50:54 +03:00

Author

Owner

@MaxXor commented on GitHub (Jun 12, 2020):

@dogo99 It was much simpler, the local window size was set to (0,0) when minimized.

@azsde Thanks for the report. It's fixed in github.com/quasar/Quasar@4c4cde446d

@MaxXor commented on GitHub (Jun 12, 2020): @dogo99 It was much simpler, the local window size was set to (0,0) when minimized. @azsde Thanks for the report. It's fixed in https://github.com/quasar/Quasar/commit/4c4cde446d1d39d917bf2459916c3aacf89579fd