| 2011-05-22 21:41:44 |
Benjamin Kaduk |
bug |
|
|
added bug |
| 2011-10-03 19:45:26 |
Launchpad Janitor |
emacs23 (Ubuntu): status |
New |
Confirmed |
|
| 2011-10-03 20:05:45 |
Brian Gernhardt |
bug watch added |
|
http://debbugs.gnu.org/cgi-bin/bugreport.cgi?bug=4970 |
|
| 2011-10-04 07:18:30 |
era |
bug task added |
|
emacs |
|
| 2011-10-10 16:04:29 |
Warren Seine |
bug |
|
|
added subscriber Warren Seine |
| 2011-11-28 09:59:25 |
Andres Freund |
bug |
|
|
added subscriber Andres Freund |
| 2012-05-07 15:40:12 |
Marius B. Kotsbak |
bug |
|
|
added subscriber Marius Kotsbak |
| 2012-05-07 15:41:19 |
Marius B. Kotsbak |
emacs23 (Ubuntu): status |
Confirmed |
Incomplete |
|
| 2012-05-08 15:39:39 |
Marius B. Kotsbak |
emacs23 (Ubuntu): status |
Incomplete |
Fix Released |
|
| 2012-05-08 17:00:58 |
Marius B. Kotsbak |
bug task added |
|
lucid-backports |
|
| 2012-05-08 17:22:36 |
Marius B. Kotsbak |
lucid-backports: status |
New |
Confirmed |
|
| 2012-05-08 17:45:15 |
Iain Lane |
bug task deleted |
lucid-backports |
|
|
| 2012-05-08 17:53:50 |
Brian Gernhardt |
description |
Binary package hint: emacs23
On several systems that I maintain, we occasionally see user's emacs processes that are using 100% of a CPU, usually when that user is not even logged in. Some follow-up with the users seems to indicate that this can happen when emacs is running in an ssh session, and ssh is terminated uncleanly.
I have been able to reproduce this somewhat-reliably (say, one time in five) by starting emacs, entering M-x shell, running 'yes', and then using the ssh escape ~. to end my session. The emacs process lives, continuing to use CPU (and consume more memory, which is presumably tied to my test case continuing to produce output to an emacs buffer). I have obtained a core file for such a process by attaching to it with gdb and using the 'gcore' command, but my build with DEB_BUILD_OPTIONS=debug does not seem to have preserved debug symbols (I guess I need nostrip as well?), so it's unclear how useful it is. (It's also 700M, due to the aforementioned RAM usage ballooning.)
I looked at the NEWS file for upstream emacs 23.2 and 23.3 and didn't see anything that looked relevant to this issue, so I suspect it's still a problem.
My testing has been done on:
root@caspian:~# uname -a
Linux caspian 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:05:27 UTC 2010 x86_64 GNU/Linux
root@caspian:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.04.1 LTS
Release: 10.04
Codename: lucid
And I've been using the source package version 23.1+1-4ubuntu7.2 |
(Description updated by Brian Gernhardt)
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. |
|
| 2012-05-08 17:57:29 |
Brian Gernhardt |
description |
(Description updated by Brian Gernhardt)
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. |
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. |
|
| 2012-05-08 18:11:00 |
Marius B. Kotsbak |
tags |
|
patch |
|
| 2012-05-08 18:13:12 |
Marius B. Kotsbak |
bug watch added |
|
https://bugzilla.novell.com/show_bug.cgi?id=556175 |
|
| 2012-05-08 18:13:12 |
Marius B. Kotsbak |
bug task added |
|
emacs23 (openSUSE) |
|
| 2012-05-08 19:17:18 |
Bug Watch Updater |
emacs23 (openSUSE): status |
Unknown |
Fix Released |
|
| 2012-05-08 19:17:18 |
Bug Watch Updater |
emacs23 (openSUSE): importance |
Unknown |
Medium |
|
| 2012-05-08 22:52:31 |
Marius B. Kotsbak |
bug watch added |
|
https://bugzilla.redhat.com/show_bug.cgi?id=732157 |
|
| 2012-05-08 22:52:31 |
Marius B. Kotsbak |
bug task added |
|
fedora |
|
| 2012-05-08 22:54:43 |
Marius B. Kotsbak |
bug watch added |
|
https://bugzilla.redhat.com/show_bug.cgi?id=769673 |
|
| 2012-05-08 22:54:43 |
Marius B. Kotsbak |
fedora: remote watch |
Red Hat Bugzilla #732157 |
Red Hat Bugzilla #769673 |
|
| 2012-05-08 23:20:19 |
Marius B. Kotsbak |
attachment added |
|
0001-Added-upstream-patch-for-LP-786730.patch https://bugs.launchpad.net/fedora/+bug/786730/+attachment/3137736/+files/0001-Added-upstream-patch-for-LP-786730.patch |
|
| 2012-05-08 23:26:08 |
Marius B. Kotsbak |
attachment added |
|
Trying again. Without the changelog diff that did not apply https://bugs.launchpad.net/fedora/+bug/786730/+attachment/3137739/+files/0001-Added-upstream-patch-for-LP-786730.patch |
|
| 2012-05-08 23:26:24 |
Marius B. Kotsbak |
attachment removed |
0001-Added-upstream-patch-for-LP-786730.patch https://bugs.launchpad.net/fedora/+bug/786730/+attachment/3137736/+files/0001-Added-upstream-patch-for-LP-786730.patch |
|
|
| 2012-05-09 12:12:55 |
Marius B. Kotsbak |
summary |
emacs spins when ssh is uncleanly terminated |
[10.04 LTS] emacs spins when ssh is uncleanly terminated |
|
| 2012-05-09 12:47:09 |
Marius B. Kotsbak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2012-05-09 15:54:35 |
Clint Byrum |
nominated for series |
|
Ubuntu Lucid |
|
| 2012-05-09 15:54:35 |
Clint Byrum |
bug task added |
|
emacs23 (Ubuntu Lucid) |
|
| 2012-05-09 15:54:45 |
Clint Byrum |
emacs23 (Ubuntu Lucid): status |
New |
Fix Committed |
|
| 2012-05-09 15:54:51 |
Clint Byrum |
emacs23 (Ubuntu Lucid): importance |
Undecided |
Medium |
|
| 2012-05-09 15:54:56 |
Clint Byrum |
emacs23 (Ubuntu): importance |
Undecided |
Medium |
|
| 2012-05-09 15:55:19 |
Clint Byrum |
bug |
|
|
added subscriber Clint Byrum |
| 2012-05-10 22:49:42 |
Joe Gross |
bug |
|
|
added subscriber Joe Gross |
| 2012-05-18 08:15:47 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
| 2012-05-18 08:15:49 |
Martin Pitt |
tags |
patch |
patch verification-needed |
|
| 2012-05-18 08:51:09 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/lucid-proposed/emacs23 |
|
| 2012-05-22 06:26:54 |
Jean-Baptiste Lallement |
tags |
patch verification-needed |
patch verification-done |
|
| 2012-05-25 22:50:09 |
Simon Kuhn |
bug |
|
|
added subscriber Simon Kuhn |
| 2012-05-28 10:38:10 |
Launchpad Janitor |
emacs23 (Ubuntu Lucid): status |
Fix Committed |
Fix Released |
|
| 2017-10-28 04:24:34 |
Bug Watch Updater |
fedora: status |
Unknown |
Fix Released |
|
| 2017-10-28 04:24:34 |
Bug Watch Updater |
fedora: importance |
Unknown |
Critical |
|
