[GH-ISSUE #930] RDP disconnect may causes freeze

kerem commented

2026-03-01 17:22:28 +03:00

Owner

Originally created by @itagagaki on GitHub (May 12, 2025).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/930

Originally assigned to: @VShawn on GitHub.

Reproducibility is random.

This did not happen with EnableAutoReconnect:i:0, but it may be a coincidence.

Originally created by @itagagaki on GitHub (May 12, 2025). Original GitHub issue: https://github.com/1Remote/1Remote/issues/930 Originally assigned to: @VShawn on GitHub. Reproducibility is random. This did not happen with `EnableAutoReconnect:i:0`, but it may be a coincidence.

kerem

2026-03-01 17:22:28 +03:00

closed this issue
added the
bug

stale
labels

kerem commented

2026-03-01 17:22:29 +03:00

Author

Owner

@VShawn commented on GitHub (May 12, 2025):

This did not happen with EnableAutoReconnect:i:0

there is no evidence to support this.

@VShawn commented on GitHub (May 12, 2025): > This did not happen with EnableAutoReconnect:i:0 there is no evidence to support this.

kerem commented

2026-03-01 17:22:29 +03:00

Author

Owner

@itagagaki commented on GitHub (May 12, 2025):

This did not happen with EnableAutoReconnect:i:0

there is no evidence to support this.

I think you've said similar things before, but I don't understand why you think that.

@itagagaki commented on GitHub (May 12, 2025): > > This did not happen with EnableAutoReconnect:i:0 > > there is no evidence to support this. I think you've said similar things before, but I don't understand why you think that.

kerem commented

2026-03-01 17:22:29 +03:00

Author

Owner

@itagagaki commented on GitHub (May 12, 2025):

Reproducibility is random.

This did not happen with EnableAutoReconnect:i:0, but it may be a coincidence.

Happened in this case as well.

@itagagaki commented on GitHub (May 12, 2025): > Reproducibility is random. > > This did not happen with `EnableAutoReconnect:i:0`, but it may be a coincidence. Happened in this case as well.

kerem commented

2026-03-01 17:22:29 +03:00

Author

Owner

@itagagaki commented on GitHub (May 12, 2025):

This issue blocks #878

@itagagaki commented on GitHub (May 12, 2025): This issue blocks #878

kerem commented

2026-03-01 17:22:29 +03:00

Author

Owner

@VShawn commented on GitHub (May 13, 2025):

It's also possible that this issue is related to switching to NET9. After the switch, I received a lot of feedback about programs freezing on the MS STORE, so I have now rolled back MS STORE to the old version.

@VShawn commented on GitHub (May 13, 2025): It's also possible that this issue is related to `switching to NET9`. After the switch, I received a lot of feedback about programs freezing on the MS STORE, so I have now rolled back MS STORE to the old version.

kerem commented

2026-03-01 17:22:29 +03:00

Author

Owner

@VShawn commented on GitHub (May 14, 2025):

Perhaps it is related to the update of the AxMSTSCLib.dll dynamic library? Should I consider rolling it back?

The thought is If this issue has been occurring frequently since 1.2.0, it is likely related to the update in version 1.2.0, and the major change in version 1.2.0 for RDP is the update of the dll.

@VShawn commented on GitHub (May 14, 2025): Perhaps it is related to the update of the AxMSTSCLib.dll dynamic library? Should I consider rolling it back? The thought is If this issue has been occurring frequently since 1.2.0, it is likely related to the update in version 1.2.0, and the major change in version 1.2.0 for RDP is the update of the dll.

kerem commented

2026-03-01 17:22:29 +03:00

Author

Owner

@itagagaki commented on GitHub (May 14, 2025):

The change in AxMSTSCLib.dll does not seem to be relevant.

The phenomena occurring are as follows:

Double-click host A in the main window (host menu).
Host A is unavailable, so alternative host B is connected.
Make Host A available.
Disconnect host B on the host side.
1Remote's reconnection logic begins to work.
Connected to Host A, and Host A's desktop appears in the host view.
In some cases, the tabable window freezes at this moment (but the app's periodic database update checks continue to run).
Clicking the close button on the tab does not close it (but TabablzControl_OnPreviewMouseLeftButtonDown() is called). The close button on the tabable window closes the entire window.
Closing the tabable window freezes the main window.

My guess is that the connection between the session and the window or tab is broken during reconnection and destrosys resources or objects that should not be destroyed.

@itagagaki commented on GitHub (May 14, 2025): The change in AxMSTSCLib.dll does not seem to be relevant. The phenomena occurring are as follows: 1. Double-click host A in the main window (host menu). 2. Host A is unavailable, so alternative host B is connected. 3. Make Host A available. 4. Disconnect host B on the host side. 5. 1Remote's reconnection logic begins to work. 6. Connected to Host A, and Host A's desktop appears in the host view. 7. In some cases, the tabable window freezes at this moment (but the app's periodic database update checks continue to run). 8. Clicking the close button on the tab does not close it (but TabablzControl_OnPreviewMouseLeftButtonDown() is called). The close button on the tabable window closes the entire window. 9. Closing the tabable window freezes the main window. My guess is that the connection between the session and the window or tab is broken during reconnection and destrosys resources or objects that should not be destroyed.

kerem commented

2026-03-01 17:22:29 +03:00

Author

Owner

@VShawn commented on GitHub (May 15, 2025):

Well, it seems a bit different from what I thought. The reproduction logic is quite complex, kudos to you for being able to find it out.

then the crucial point lies on the auto reconnect logic, I considering a complete overhaul of this module.

@VShawn commented on GitHub (May 15, 2025): Well, it seems a bit different from what I thought. The reproduction logic is quite complex, kudos to you for being able to find it out. then the crucial point lies on the auto reconnect logic, I considering a complete overhaul of this module.

kerem commented

2026-03-01 17:22:29 +03:00

Author

Owner

@itagagaki commented on GitHub (May 15, 2025):

then the crucial point lies on the auto reconnect logic, I considering a complete overhaul of this module.

I hope my fixes will help with that.
https://github.com/itagagaki/1Remote/tree/fix-rdp-reconnection

@itagagaki commented on GitHub (May 15, 2025): > then the crucial point lies on the auto reconnect logic, I considering a complete overhaul of this module. I hope my fixes will help with that. https://github.com/itagagaki/1Remote/tree/fix-rdp-reconnection

kerem commented

2026-03-01 17:22:29 +03:00

Author

Owner

@VShawn commented on GitHub (May 17, 2025):

sorry, I've been quite busy with work these days and haven't had time to check GitHub.

May I ask if I can merge your branch directly, or would you prefer me to make modifications based on your work?

I have reviewed your code and it seems fine. However, 1Remote now may missing a button to cancel the reconnection for the user.

@VShawn commented on GitHub (May 17, 2025): sorry, I've been quite busy with work these days and haven't had time to check GitHub. May I ask if I can merge your branch directly, or would you prefer me to make modifications based on your work? I have reviewed your code and it seems fine. However, 1Remote now may missing a button to cancel the reconnection for the user.

kerem commented

2026-03-01 17:22:29 +03:00

Author

Owner

@itagagaki commented on GitHub (May 17, 2025):

My branch above fixes #878
However, this bug has not yet been resolved, so it should not be merged.
I mentioned the branch to you because I think the code is necessary for analyzing this bug.
If you can fix this bug, then you can merge directly or I can submit a PR.
I will investigate this bug further, but I am busy too, so I don't know which of us will finish first.

1Remote now may missing a button to cancel the reconnection for the user.

The "Dismiss" button appears and works during the reconnect process.

@itagagaki commented on GitHub (May 17, 2025): My branch above fixes #878 However, this bug has not yet been resolved, so it should not be merged. I mentioned the branch to you because I think the code is necessary for analyzing this bug. If you can fix this bug, then you can merge directly or I can submit a PR. I will investigate this bug further, but I am busy too, so I don't know which of us will finish first. > 1Remote now may missing a button to cancel the reconnection for the user. The "Dismiss" button appears and works during the reconnect process.

kerem commented

2026-03-01 17:22:30 +03:00

Author

Owner

@VShawn commented on GitHub (May 20, 2025):

After conducting several tests over the past few days, I have not encountered any freezing issues. It seems that my environment does not trigger this problem. Now I decided to halt my investigation into this matter until there are any new discoveries.

Here are the steps of my testing:

Prepare three computers: A, B, C.
Install 1Remote on A and create a new configuration： Set the main address point to B and the backup address to point to C.
Disable the auto-reconnect feature by RDP (EnableAutoReconnect = false).
Unplug the net cable from B, initiate the connection, should now connect to C.
Reconnect the cable to B and unplug the cable from C. At this point, the RDP interface will stop refreshing for about 10 seconds, but the software will not become unresponsive.
1Remote will automatically reconnect to the B host.
Unplug the network cable from B again, wait a few seconds, close the TAB window, and observe if the main window of 1Remote becomes unresponsive.

@VShawn commented on GitHub (May 20, 2025): After conducting several tests over the past few days, I have not encountered any freezing issues. It seems that my environment does not trigger this problem. Now I decided to halt my investigation into this matter until there are any new discoveries. Here are the steps of my testing: 1. Prepare three computers: A, B, C. 2. Install 1Remote on A and create a new configuration： Set the main address point to B and the backup address to point to C. 3. Disable the auto-reconnect feature by RDP (EnableAutoReconnect = false). 4. Unplug the net cable from B, initiate the connection, should now connect to C. 5. Reconnect the cable to B and unplug the cable from C. At this point, the RDP interface will stop refreshing for about 10 seconds, but the software will not become unresponsive. 6. 1Remote will automatically reconnect to the B host. 7. Unplug the network cable from B again, wait a few seconds, close the TAB window, and observe if the main window of 1Remote becomes unresponsive.

kerem commented

2026-03-01 17:22:30 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jun 20, 2025):

This issue is stale because it has been open for 30 days with no activity.

@github-actions[bot] commented on GitHub (Jun 20, 2025): This issue is stale because it has been open for 30 days with no activity.

kerem commented

2026-03-01 17:22:30 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jul 4, 2025):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (Jul 4, 2025): This issue was closed because it has been inactive for 14 days since being marked as stale.

Rows
Columns

[GH-ISSUE #930] RDP disconnect may causes freeze #2675