RustDesk hangs when connecting to the local computer ID

When I enter my own RustDesk computer ID into the Control Remote Desktop field and click Connect, the application hangs and becomes completely unresponsive.

RustDesk should detect that the destination ID is the same as the current computer's own ID and prevent the connection attempt.

For example, RustDesk could display a warning such as:

Cannot connect to this device.
The destination ID is the same as this computer's own ID.

Then the connection attempt should be cancelled without causing the application to hang.

Suggested fix

Add a validation check before initiating a remote connection. If the destination ID is the same as the current computer's own ID, RustDesk should display a clear warning and automatically cancel the connection attempt.

This would prevent self-connection attempts and avoid the application becoming unresponsive.

No file or test is named. Start by locating the remote connection entry point and the logic that knows the current computer's ID. Done means entering the local ID shows a clear warning, cancels the attempt, and no longer hangs the application.