-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
explorer.exe crashes cause FancyWM to crash #31
Comments
@veselink1 Just letting you know I did report issue to Microsoft via feedbackhub. Let's hope it won't take yrs |
@mataslib Thanks for reporting to Microsoft. This is in fact caused by explorer.exe crashing. When not running, the virtual desktop service is unavailable, so FancyWM has no way of knowing which windows belong to which virtual desktop. I plan to improve the error handling system, by allowing the user to force the application to continue running, ignoring any errors, but this will likely not be implemented anytime soon. |
just leaving here feedback hub link https://aka.ms/AAfkv1q for upvote. |
Explorer crashes no longer crash FancyWM as of v2.6.0 in Store now (as long as explorer starts again in 10s). |
couldn't test it since explorer isn't crashing anymore in my case |
Describe the bug
Fancy crashes often with error "explorer.exe just crashed and this caused virtual desktops...". It always happens in win+tab mode, eg. when dragging app to another vir. desktop. Dragging chrome with 50 tabs is 100% crash. Seems like windows issue though, weird behaviour (like explorer.exe indeed does crash) happens even without Fancy running :/.
To Reproduce
Desktop (please complete the following information):
Device name mataslib
Processor Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz 2.21 GHz
Installed RAM 64,0 GB (63,7 GB usable)
System type 64-bit operating system, x64-based processor
Pen and touch Pen and touch support with 10 touch points
Edition Windows 11 Pro
Version 21H2
Installed on 09.11.2021
OS build 22000.469
Experience Windows Feature Experience Pack 1000.22000.469.0
The text was updated successfully, but these errors were encountered: