Bug 405674 - high cpu usage caused by acroread
Summary: high cpu usage caused by acroread
Status: RESOLVED DUPLICATE of bug 363381
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Mike Fabian
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-02 10:40 UTC by Daniele Frijia
Modified: 2008-07-03 15:12 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniele Frijia 2008-07-02 10:40:34 UTC
Sometimes (dont know what I did) there is a "ld-linux.so.2" in the top-list using 50-55% of cpu.

If I logout and relogin it's gone, but sometimes it shows up again.

pstree says, that it's  "fork" of init.

I can kill the process, but dont know, if it's bad. Everything SEEMS to work fine :).

I cannot reproduce the bug.
Comment 1 Daniele Frijia 2008-07-02 14:04:51 UTC
I'm stupid. I found the bug. Its acroread. top didn show me the rest of the line:
ps aux|grep ld-lin
cosmo    12881  2.6  8.2 361556 168544 ?       S    12:25   5:43 /lib/ld-linux.so.2 /usr/lib/Adobe/Reader8/Reader/intellinux/bin/acroread --display :0.0 -progressPipe 3 -exitPipe 4
cosmo    25011 15.0 21.6 862888 445216 ?       S    14:02  18:17 /lib/ld-linux.so.2 /usr/lib/Adobe/Reader8/Reader/intellinux/bin/acroread --display :0.0 -progressPipe 3 -exitPipe 4
cosmo    25228 12.8 21.3 740892 438340 ?       S    14:03  15:28 /lib/ld-linux.so.2 /usr/lib/Adobe/Reader8/Reader/intellinux/bin/acroread --display :0.0 -progressPipe 3 -exitPipe 4
cosmo    30845  8.6 18.8 459848 386652 ?       S    14:43   6:56 /lib/ld-linux.so.2 /usr/lib/Adobe/Reader8/Reader/intellinux/bin/acroread --display :0.0 -progressPipe 3 -exitPipe 4

So still a bug for here or for adobe?
Comment 2 Mike Fabian 2008-07-03 15:12:23 UTC
I think this is a duplicate of bug #363381.


*** This bug has been marked as a duplicate of bug 363381 ***