Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash: The instruction at 0x00007FF82062930C referenced memory at 0x0000000000000000 #7412

Closed
Tracked by #7342
L-U-C-K-Y opened this issue Mar 17, 2024 · 2 comments
Closed
Tracked by #7342
Labels
bug Something isn't working unreproducible Can not be reproduced

Comments

@L-U-C-K-Y
Copy link

Bug Description

We have a couple RustDesk installations that are crashing after a while with the following error:

"The instruction at 0x00007FF82062930C referenced memory at 0x0000000000000000. The operation read could not be performed in memory. Click "OK" to terminate the program."

It happens without connecting to it. After connecting with another remote management tool, I restart the server and things are working again.

image

How to Reproduce

Unfortunately, I do not know how to reproduce the error, it just happens after a while.

Expected Behavior

I would expect RustDesk not to crash.

Operating system(s) on local side and remote side

None on the local side -> Windows 11 on the remote side

RustDesk Version(s) on local side and remote side

None on the local side -> rustdesk-1.2.3-1-x86_64

Screenshots

image

Additional Context

No response

@L-U-C-K-Y L-U-C-K-Y added the bug Something isn't working label Mar 17, 2024
@rustdesk
Copy link
Owner

tracked by #7342

@rustdesk rustdesk added the unreproducible Can not be reproduced label Mar 17, 2024
@danielmarschall
Copy link
Contributor

@L-U-C-K-Y You could try running WinDbg to check where the crash happens, and then write the results here. ( Explanation and debug build here #7543 (reply in thread) ).

Also, please try the nightly build which will be released tomorrow, because RustDesk now uses a new "Flutter" version. Then we could rule out the possibility that the crash was caused by an old Flutter version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working unreproducible Can not be reproduced
Projects
None yet
Development

No branches or pull requests

3 participants