Mailinglist Archive: opensuse (5130 mails)

< Previous Next >
10.1: Extreme slow startup of acroread
  • From: Michael Nelson <michaelnel@xxxxxxxxxxx>
  • Date: Sat, 27 May 2006 19:14:26 -0700
  • Message-id: <20060528021426.GA8750@xxxxxxxxxxxxxxxxxx>
Hello

Since upgrading my system (1.8GHz P4 with 512MB RAM and Ultra 160 SCSI
drives), the startup time of some programs (most particularly, acrobat
reader) have gotten REALLY long.

For instance, it takes a minute and 4 seconds for the acroread window
to appear on the display after typing "/usr/bin/acroread" at a shell
prompt.

$ time acroread

real 1m4.604s
user 1m1.764s
sys 0m1.144s

When I was running 10.0 I never measured the startup time because it was
very quick, but I would estimate it used to take 5 seconds max to start
up.

I have run strace on it under 10.1, and the summary shows this in the first
few lines:

% time seconds usecs/call calls errors syscall
------ ----------- ----------- --------- --------- ----------------
45.68 0.087192 632 138 65 waitpid
14.09 0.026892 1 24464 425 read
10.42 0.019895 1 19085 17566 open
10.20 0.019469 87 224 madvise
4.81 0.009182 214 43 execve
2.37 0.004527 17 262 getdents64
2.21 0.004210 4 1020 510 access
2.14 0.004081 2 1932 296 stat64
2.10 0.003999 3 1476 poll
1.40 0.002667 6 477 munmap
1.24 0.002373 47 50 writev
0.99 0.001894 1 2700 write
0.60 0.001139 3 391 _llseek
0.00 0.000000 0 2 shmctl

... many lines deleted...

------ ----------- ----------- --------- --------- ----------------
100.00 0.190871 73318 18980 total

It seems to be spending over 45% of the time on waitpid syscalls, and it
also did over 19,000 open calls of which about 92% resulted in failure.

I thought I might have a bad LD_LIBRARY_PATH, but it is not set in
either my or root's environment. There was some cruft in
/etc/ld.so.conf, but I removed that and it didn't make any difference.

When I look at the detailed tracelog I can see that the vast majority of
open calls result in ENOENT (no such file or directory) or EACCES
(Permission denied). Most are ENOENT though, because it seems to be
looking for stuff where it isn't... thousands and thousands of times. I
can even see instances where it did a STAT on the file and the STAT
failed, then it immediately tried to open the file in the same location,
which naturally failed too.

I thought it might have something to do with my environment as a
particular user, so I tried it as root (same problem) and even created a
brand new virgin user and that account sees the same problem.

Any ideas on how to troubleshoot and fix this? Oh, I also tried
removing the SuSE-supplied acrobat rpm and replacing it with the one
from the Adobe site... no improvement.

Thanks in advance for any help and / or suggestions!

Michael

---

San Francisco, CA

< Previous Next >