-
-
Notifications
You must be signed in to change notification settings - Fork 432
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
[Bug]The app CRASHED when the memory usage is over 85%. #191
Comments
All I can say is that when I did this on my laptop with 3GB of RAM, it caused the whole system to hang due to heavy load in the form of constant cleaning until the memory was less than 85%, which caused some applications to crash and this suspended and (actually) reduced memory usage. I also see this as a problem, because in some cases, when the system can't free up enough memory, memreduct runs something like a routine in a loop "While memory used > user value" and if this time to run memreduct - it crashed on that system. This problem existed 2-3 years ago, but at this moment it is not known whether it remains. I can't check right now, as that laptop has some system issues, but it's an i3 370m with integrated graphics Now on the PC it just cleans the memory cyclically, but the applications stay in place (maybe the M.2 SSD helps?) and messages are sent every second that the memory is cleared (like normal operation) |
Checklist
App version
3.4
Windows version
Windows 11 Pro Insider Preview. Build 25352.zn_release.20230422-2250
Steps to reproduce
Expected behavior
DO NOT CRASH
Actual behavior
It Crashed
Logs
No response
The text was updated successfully, but these errors were encountered: