-
Notifications
You must be signed in to change notification settings - Fork 13
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] CPU usage 100% when offline #108
Comments
Hi, I checked here and I can reproduce it too. I haven't checked the code for the root cause yet, but based on my testing it seems a temporary workaround is to manually start nmail in offline mode: This is a quite bad bug though, so I'll definitely look into fixing it as soon as I get a chance. |
Just posting because I observed the same issue long before 3.73, probably even early last year, so it might be necessary to look into other commits too (I hope I am not wrong though). Usually this would happen when I put my laptop to sleep and then wake it the next day and have no Internet connection, but still have nmail instances running in Termux. Apparently I failed to report it, sorry. It might be partly related to #74? I suppose the CPU hog when offline could be an extension over longers duration of the CPU spike when trying to connect? |
I can confirm that this is a very old bug. It affects the scenario when I have some idea on how it should be fixed. Will prepare a fix and perform some testing on my side before pushing a fix. |
This should be fixed with above commit. Please let me know if you're still encountering any issues. |
I I've noticed that CPU usage goes 100% when
nmail
is started offline. It must have appeared somewhere around version 3.74 I think. The bug mustn't be there when I started using nmail; I'm often offline plus the fan of my CPU makes noticeable noise when going 100%. I initially thought it was incidental but I can reproduce it by simply opening nmail without an active internet connection. I'm attaching a verbose log file.nmail--offline-100percent-log.txt
The text was updated successfully, but these errors were encountered: