starred/1Remote

Fork 0

mirror of https://github.com/1Remote/1Remote.git synced 2026-04-25 13:36:03 +03:00

[GH-ISSUE #805] Crash if continue to drag the edge of the RDP window too hard #2577

New issue

Closed

opened 2026-03-01 17:21:37 +03:00 by kerem · 3 comments

kerem commented

2026-03-01 17:21:37 +03:00

Owner

Originally created by @itagagaki on GitHub (Dec 9, 2024).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/805

Originally assigned to: @VShawn on GitHub.

As I reported in a comment to #797, dragging very hard to resize the RDP window causes Explorer to freeze; pressing Ctrl+Alt+Del and Esc brings Explorer back, but 1Remote remains crashed and has to be forced to quit.

Although #797 has been fixed, this crash problem has still been observed, so I file it here.

Workaround:
Avoid furious operation. Probably not necessary

Originally created by @itagagaki on GitHub (Dec 9, 2024). Original GitHub issue: https://github.com/1Remote/1Remote/issues/805 Originally assigned to: @VShawn on GitHub. As I reported in a comment to #797, dragging very hard to resize the RDP window causes Explorer to freeze; pressing `Ctrl`+`Alt`+`Del` and `Esc` brings Explorer back, but 1Remote remains crashed and has to be forced to quit. Although #797 has been fixed, this crash problem has still been observed, so I file it here. Workaround: Avoid furious operation. Probably not necessary

kerem

2026-03-01 17:21:37 +03:00

closed this issue
added the
bug

priority-low
labels

kerem commented

2026-03-01 17:21:38 +03:00

Author

Owner

@VShawn commented on GitHub (Dec 10, 2024):

I did not observe this bug. As I dragged the edge from the left side of the screen to the right side and back to the left side multiple times within one second.

@VShawn commented on GitHub (Dec 10, 2024): I did not observe this bug. As I dragged the edge from the left side of the screen to the right side and back to the left side multiple times within one second.

kerem commented

2026-03-01 17:21:38 +03:00

Author

Owner

@itagagaki commented on GitHub (Dec 10, 2024):

I have just been able to reproduce it just now. But I think it has become less reproducible. So it makes it harder to find the cause. I tried to find conditions that would make it easier to reproduce the problem, but I couldn't find anything. I have a feeling that it might have something to do with timing, but I don't know.

However, the fact that the frequency of the problem has decreased is good for the use of this app, and as I said, it doesn't seem to occur in normal, reasonable use, so I think the priority of investigating this issue can be lowered.

@itagagaki commented on GitHub (Dec 10, 2024): I have just been able to reproduce it just now. But I think it has become less reproducible. So it makes it harder to find the cause. I tried to find conditions that would make it easier to reproduce the problem, but I couldn't find anything. I have a feeling that it might have something to do with timing, but I don't know. However, the fact that the frequency of the problem has decreased is good for the use of this app, and as I said, it doesn't seem to occur in normal, reasonable use, so I think the priority of investigating this issue can be lowered.

kerem commented

2026-03-01 17:21:39 +03:00

Author

Owner

@itagagaki commented on GitHub (Feb 4, 2025):

That doesn't happen anymore these days. I think we can close this once.

@itagagaki commented on GitHub (Feb 4, 2025): That doesn't happen anymore these days. I think we can close this once.

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/1Remote#2577

No description provided.

Rows
Columns