emacs crashes when closing gdm

Bug #688352 reported by Jens Kubieziel
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
emacs-snapshot (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: emacs-snapshot

I'm using Ubuntu 10.04.1 LTS with emacs-snapshot 1:20090909-1. Other packages which are involved are GNU screen 4.0.3-14ubuntu1.2 and dbus 1.2.16-2ubuntu4.

Steps to reproduce:
1.) I assume that I'm already logged in to GNOME.
2.) Open a terminal (gnome-terminal 2.30.2-0ubuntu1, in my case)
3.) Open GNU screen ('screen -c /dev/null' or with any .screenrc)
4.) Open GNU Emacs inside GNU screen.
5.) Detach screen session (<Ctrl-a+DD)
6.) Log out from GNOME.

Now GNU Emacs generates a high load, uses lots of CPU and even more RAM (usually complete RAM plus same amount of swap space).

I made a strace and the following sequence seems to be the problem:
connect(5, {sa_family=AF_FILE, path=@"/tmp/dbus-qIVcDA4mSE"}, 23) = -1 ECONNREFUSED (Connection refused)
close(5) = 0
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig -icanon -echo ...}) =
 0
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig -icanon -echo ...}) =
 0
ioctl(3, SNDCTL_TMR_STOP or TCSETSW, {B38400 opost isig -icanon -echo ...}) = 0
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig -icanon -echo ...}) = 0
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig -icanon -echo ...}) = 0
write(3, "\7", 1) = 1
poll([{fd=8, events=POLLIN}], 1, 0) = 0 (Timeout)
socket(PF_FILE, SOCK_STREAM, 0) = 5

This repeats until I SIGKILLed emacs.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: emacs-snapshot 1:20090909-1
ProcVersionSignature: Ubuntu 2.6.32-26.48-generic 2.6.32.24+drm33.11
Uname: Linux 2.6.32-26-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Dec 9 23:56:00 2010
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/usr/bin/zsh
SourcePackage: emacs-snapshot

Revision history for this message
Jens Kubieziel (qbi) wrote :
Revision history for this message
quazgar (quazgar) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.