Fix panic at redraw event in non redraw phase#1422
Conversation
|
I was wrong again. This does not fix the issue. |
|
@Kethku this PR also has a change to provide more information when the panic happens. Could you reproduce the issue with this fix and report back the panic message ? |
|
I just pulled the resent change and the error seems to have gone away. I am trying reverting the most recent change to confirm the issue reappears. |
|
Ok it looks like on this machine I don't encounter the error which is very concerning. Remoting in to try from my other machine now. |
|
Arg. I can't get the error to reproduce in any environment anymore... |
|
I had the same problem. Sometimes I can reproduce the issue 3 times in a row and sometimes it just won't reproduce. Very frustrating. |
|
Alrighty then. I can neither confirm nor deny at this moment if this PR fixes the issue |
|
I have updated my app to target this hotfix and will run with it until I find the error. I will report back in a couple of days if I have not seen it |
|
This PR needs to be reviewed thoroughly. Although it seems to fix the issue, it feels like a workaround of the symptom. The root cause of the issue might still be there. One thing, for example, it that the panic cannot be reached anymore. So why keep it ? |
They do happen so just handle them
1ddd984 to
277e352
Compare
|
With this patch I was able to drag/resize a winit window (on Windows 10) and it did not panic. I was able to consistently repro on master @ 4eddd1e using the resizable example This may not be an apples to apples comparison though as this branch is based on |
|
Superseded by #1461 |
cargo fmthas been run on this branchcargo docbuilds successfullyCHANGELOG.mdif knowledge of this change could be valuable to users