[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

XEmacs has slow startup



XEmacs takes an annoyingly long time to start up. It does not appear to
be using CPU or doing disk access--it just "pauses" for a few seconds
while starting.

I tried an "strace xemacs" to see what system calls were being made. 
During the slow part of startup, here's what it was doing:

setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 0}}, NULL) = 0
uname({sys="Linux", node="funkybox", ...}) = 0
socket(PF_UNIX, SOCK_STREAM, 0)         = 6
connect(6, {sun_family=AF_UNIX, sun_path="/tmp/.sockets/audio0"}, 22) =
-1 ENOENT (No such file or directory)
close(6)                                = 0
nanosleep({1, 0}, {1, 0})               = 0
socket(PF_UNIX, SOCK_STREAM, 0)         = 6
connect(6, {sun_family=AF_UNIX, sun_path="/tmp/.sockets/audio0"}, 22) =
-1 ENOENT (No such file or directory)
close(6)                                = 0
nanosleep({1, 0}, {1, 0})               = 0
socket(PF_UNIX, SOCK_STREAM, 0)         = 6
connect(6, {sun_family=AF_UNIX, sun_path="/tmp/.sockets/audio0"}, 22) =
-1 ENOENT (No such file or directory)
close(6)                                = 0
nanosleep({1, 0}, {1, 0})               = 0
socket(PF_UNIX, SOCK_STREAM, 0)         = 6
connect(6, {sun_family=AF_UNIX, sun_path="/tmp/.sockets/audio0"}, 22) =
-1 ENOENT (No such file or directory)
close(6)                                = 0
nanosleep({1, 0}, {1, 0})               = 0
socket(PF_UNIX, SOCK_STREAM, 0)         = 6
connect(6, {sun_family=AF_UNIX, sun_path="/tmp/.sockets/audio0"}, 22) =
-1 ENOENT (No such file or directory)
close(6)                                = 0
nanosleep({1, 0}, {1, 0})               = 0
socket(PF_UNIX, SOCK_STREAM, 0)         = 6
connect(6, {sun_family=AF_UNIX, sun_path="/tmp/.sockets/audio0"}, 22) =
-1 ENOENT (No such file or directory)
close(6)                                = 0
fcntl(5, F_SETFL, O_RDWR|O_NONBLOCK|O_ASYNC) = 0

I haven't looked at the XEmacs source code yet to figure out what it's
doing, or why.  My unenlightened guess is that it's trying to open some
audio stream, retrying several times, and eventually giving up.

Does anyone know what it's doing here, whether it's important, and
whether there is some way to either make it work better or to turn it
off completely?

Thanks,
Kris


Reply to: