-
Notifications
You must be signed in to change notification settings - Fork 39
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
The latest version looks become less stable #66
Comments
I faced similar issues, if any program goes unresponsive, DWM crashes, and any open programs disappear |
When debugging the following error is thrown, in this case it occurred when Exception thrown at 0x00007FFC8131246E (vcruntime140.dll) in dwm-win32.exe: 0xC0000005: Access violation reading location 0x0000000000000000. |
yep, i faced this too... but i was too clueless to even be able to file as an issue. glad i accidently came to issues and read this. i am also on win 10 22h2. it happened with vivaldi browser incognito mode launched by debug task of vscodium for me. |
hey @nir9 ! can you take a look 😃 |
|
@goyalyashpal The general issue is that dwm-win32 freezes when a program becomes unresponsive? |
no, but rather that all the opened apps disappear - often times they seem to get closed, and rarely they get minimized. |
@goyalyashpal The open apps seem to disappear when dwm-win32 crashes, you can use winlister to show again the windows that disappeared. Working on a PR that improves the stability of dwm-win32 by not managing windows that are not responding - #71 |
Would it be viable to save a list of open windows, and automatically show them again on dwm-win32 start? Then the crashes wouldn't be a huge inconvenience, as we would just run dwm-win32 again. As they still occur randomly every now and then, even with this new PR. Update: added a simple try except block to catch exceptions, and unmanage the windows before crashing and that seems to work fine PR: #75.
|
It seems easier to crash than before.
Not quite sure, but do have the feeling.
The text was updated successfully, but these errors were encountered: