Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I used nano earlier during the day and I came back to my computer to find that almost 100% CPU usage, and nothing running. Strangely this did not slow the computer at all, but it was strange. I ran "top" and found nano was responsible, though I had closed the Terminal it was running in earlier (probably why it was unhappy).
I just killed the process, and everything went back to normal.
Is this normal? Is this a bug? How do I find out what it was doing?
I've tried reproducing it and I can't I can't see the problem would be with nano though...its such a small simple program, which leads me to think something else must have messed up. Either way, I guess its not worth putting too much time towards.
I don't know if it's the same issue, but if I use a sudo aptitude in a terminal window and don't exit the program but just close the window, I get the same (aptitude using 100% cpu). That is due to aptitude being a root process that can't be shut down from the terminal window which only has user privileges. I think aptitude then tries to do some I/O without having a terminal and thus starts munching cpu out of frustration.
As I said, it might not be related but it looks the same.
__
Rud
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.