|
Bugzilla – Full Text Bug Listing |
| Summary: | preload uses a lot of cpu | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | David Kerkhof <dutchkind> |
| Component: | Basesystem | Assignee: | Stephan Kulow <coolo> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | gankov, matz |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | /var/cache/preload/prepared | ||
|
Description
David Kerkhof
2009-10-23 17:04:34 UTC
I have same issue, for GNOME. And i can test. I use RC1. The preload process or the prepare_preload process? Can you install preload-debuginfo and gdb -p $(pidof preload) and then type bt? It was the preload process, not the prepare_preload process. But the funny thing is I cannot repeat it anymore, I have been watching closely but both mentioned processes come up and then either close or don't use much cpu anymore, so it seems no problem at the moment. I also noted that my ram memory usage has gone down without doing a thing to it. I used to have only 1 Gb free of the 3Gb I have, and now it is after boot 2.3Gb free, which is more normal compared to kde3 in opensuse 11, although still more than that used to use. So for now can't give more info on this bug, sorry to have bothered with this. if you notice it, attach /var/cache/preload/prepared here Created attachment 324628 [details]
/var/cache/preload/prepared
I saw this problem as well.
top: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 386 root 20 0 10844 1120 280 S 95 0.0 254:14.26 preload Uh. Well, the prepared file contains extremely many commands (10600), but that alone shouldn't lead to this issue. I can't reproduce it with that input on my machine, but that's no wonder as I don't have all of the mentioned files here. Maybe we can login to your machine (if it's reproducable again)? Michael and me looked at it and are confident that both bugs are duplicates. *** This bug has been marked as a duplicate of bug 551801 *** |