You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Sentry reported a crash in a user's instance of the Recut app.
panic: assertion `left == right` failed: this shouldn't be possible. please open an issue with Tauri. error code: -1
left: 0
right: 49862
?, in <unknown>
?, in <unknown>
?, in <unknown>
?, in <unknown>
?, in <unknown>
...
(14 additional frame(s) were not displayed)
Unfortunately there's no stack trace info here, but I traced the error message to this function in tao:
"this shouldn't be possible. please open an issue with Tauri. error code: {}",
result.0
);
msg.lParam.0asu32
}
}
Steps To Reproduce
I don't know how to reproduce this unfortunately. This one user has hit the error a few times, their machine ID is the only one I've seen it from.
Expected behavior
Looking at the code, I think the error might be that it doesn't check the return value before checking that the thread IDs always match. It looks like in my user's case the GetMessageW returned -1 and a zeroed-out msg, so msg.message was 0. Maybe it should have returned early? (I'm not sure about the downstream effects of that though)
The docs for GetMessageW say that it could return an error if the hwnd is invalid or the message pointer is invalid (maybe other reasons too).
Screenshots
No screenshots
Platform and Versions (please complete the following information):
OS: Windows (unsure which version unfortunately; Sentry only says "windows" without a version number)
Rustc: 1.77.1
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
Sentry reported a crash in a user's instance of the Recut app.
Unfortunately there's no stack trace info here, but I traced the error message to this function in tao:
tao/src/platform_impl/windows/event_loop.rs
Lines 358 to 374 in c49b83a
Steps To Reproduce
I don't know how to reproduce this unfortunately. This one user has hit the error a few times, their machine ID is the only one I've seen it from.
Expected behavior
Looking at the code, I think the error might be that it doesn't check the return value before checking that the thread IDs always match. It looks like in my user's case the
GetMessageW
returned-1
and a zeroed-outmsg
, somsg.message
was 0. Maybe it should have returned early? (I'm not sure about the downstream effects of that though)The docs for GetMessageW say that it could return an error if the
hwnd
is invalid or the message pointer is invalid (maybe other reasons too).Screenshots
No screenshots
Platform and Versions (please complete the following information):
OS: Windows (unsure which version unfortunately; Sentry only says "windows" without a version number)
Rustc: 1.77.1
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: