Launchpad has imported 3 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=769673.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2011-12-21T17:15:15+00:00 RHEL wrote: This bug has been copied from bug #732157 and has been proposed to be backported to 6.2 z-stream (EUS). Reply at: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/786730/comments/10 ------------------------------------------------------------------------ On 2012-01-09T12:23:45+00:00 Miroslav wrote: Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Emacs did not properly terminate if it was started remotely and the remote client session was closed while Emacs was suspended. Under these conditions, Emacs entered an infinite loop in the code and gradually consumed all available computer resources, which caused the system to become unstable. With this update, Emacs has been modified, and it now terminates correctly when the remote session is closed. Reply at: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/786730/comments/11 ------------------------------------------------------------------------ On 2012-01-23T09:11:33+00:00 errata-xmlrpc wrote: Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0042.html Reply at: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/786730/comments/12 ** Changed in: fedora Status: Unknown => Fix Released ** Changed in: fedora Importance: Unknown => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs23 in Ubuntu. https://bugs.launchpad.net/bugs/786730 Title: [10.04 LTS] emacs spins when ssh is uncleanly terminated Status in GNU Emacs: Unknown Status in emacs23 package in Ubuntu: Fix Released Status in emacs23 source package in Lucid: Fix Released Status in Fedora: Fix Released Status in emacs23 package in openSUSE: Fix Released Bug description: When emacs is running in an ssh session and ssh is terminated uncleanly, it begins to use 100% CPU and slowly but constantly increase its used memory. [Impact] In a department with approximately 50 desktops, one publicly accessible server, and a couple hundred users, I have to kill on average one emacs process a day. If left alone, those processes not only slow down the machine (by using up CPU time) but also eventually trigger the OOM killer when their memory usage exceeds the amount of available swap space. Unfortunately, the Linux OOM killer is not 100% accurate at removing the cause and I have seen other long-running high-memory processes. While I have heard no complaints about data loss, it is possible. [Development Fix] Newer versions of Ubuntu have fixed this problem by having newer versions of emacs. The issue was fixed in 23.2a, so all Ubuntu packages > 23.2 are fixed. [Stable Fix] The fix from emacs applies cleanly to the source for 23.1 and can be found in their git repository: http://git.savannah.gnu.org/cgit/emacs.git/patch/?id=1857569af70493e9dcd446c8bfb029096b355593 [Test Case] 1) ssh to localhost 2) start emacs 3) Control-Z 4) Enter, tilde, period (to kill the SSH session) 5) emacs starts spinning and eating memory (verified by top) [Regression Portential] Given that the fix only affects emacs when it is exiting, it is unlikely to cause any user regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/emacs/+bug/786730/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
