Bug 252043 - Slab takes 10 seconds to show after waking up from STR
Summary: Slab takes 10 seconds to show after waking up from STR
Status: RESOLVED DUPLICATE of bug 300289
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Beta 3
Hardware: Other Other
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: James Krehl
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-07 06:09 UTC by Magnus Boman
Modified: 2007-09-18 06:11 UTC (History)
1 user (show)

See Also:
Found By: Other
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 Magnus Boman 2007-03-07 06:09:42 UTC
After waking the laptop up from STR, it takes 10 seconds for Slab to show up in the panel.

During these 10 seconds, it's hogging the CPU. Strace shows houndreds of these messages;

writev(21, [{"l\1\0\1\0\0\0\0\261f\3\0\246\0\0\0\1\1o\0,\0\0\0/org/f"..., 184}, {"", 0}], 2) = 184
gettimeofday({1173245870, 143702}, NULL) = 0
poll([{fd=21, events=POLLIN, revents=POLLIN}], 1, 25000) = 1
read(21, "l\2\1\1\10\1\0\0!\306\0\0E\0\0\0\6\1s\0\5\0\0\0:1.30\0"..., 2048) = 352
read(21, 0x83f5af8, 2048)               = -1 EAGAIN (Resource temporarily unavailable)
gettimeofday({1173245870, 144257}, NULL) = 0
gettimeofday({1173245870, 144508}, NULL) = 0
writev(21, [{"l\1\0\1\0\0\0\0\262f\3\0\213\0\0\0\1\1o\0\37\0\0\0/org"..., 160}, {"", 0}], 2) = 160
gettimeofday({1173245870, 144630}, NULL) = 0
poll([{fd=21, events=POLLIN, revents=POLLIN}], 1, 25000) = 1
read(21, "l\2\1\1i\0\0\0\"\306\0\0-\0\0\0\6\1s\0\5\0\0\0:1.30\0\0"..., 2048) = 169
read(21, 0x83f5af8, 2048)               = -1 EAGAIN (Resource temporarily unavailable)
gettimeofday({1173245870, 145488}, NULL) = 0
writev(21, [{"l\1\0\1\0\0\0\0\263f\3\0\246\0\0\0\1\1o\0,\0\0\0/org/f"..., 184}, {"", 0}], 2) = 184
gettimeofday({1173245870, 145638}, NULL) = 0
poll([{fd=21, events=POLLIN, revents=POLLIN}], 1, 25000) = 1
read(21, "l\2\1\1\10\1\0\0#\306\0\0E\0\0\0\6\1s\0\5\0\0\0:1.30\0"..., 2048) = 352
read(21, 0x83f5af8, 2048)               = -1 EAGAIN (Resource temporarily unavailable)
gettimeofday({1173245870, 146520}, NULL) = 0
writev(21, [{"l\1\0\1\0\0\0\0\264f\3\0\246\0\0\0\1\1o\0,\0\0\0/org/f"..., 184}, {"", 0}], 2) = 184
gettimeofday({1173245870, 146646}, NULL) = 0
poll([{fd=21, events=POLLIN, revents=POLLIN}], 1, 25000) = 1
read(21, "l\2\1\1\10\1\0\0$\306\0\0E\0\0\0\6\1s\0\5\0\0\0:1.30\0"..., 2048) = 352
read(21, 0x83f5af8, 2048)               = -1 EAGAIN (Resource temporarily unavailable)
gettimeofday({1173245870, 147368}, NULL) = 0
gettimeofday({1173245870, 147630}, NULL) = 0
writev(21, [{"l\1\0\1\0\0\0\0\265f\3\0\213\0\0\0\1\1o\0\37\0\0\0/org"..., 160}, {"", 0}], 2) = 160
gettimeofday({1173245870, 147753}, NULL) = 0
poll([{fd=21, events=POLLIN, revents=POLLIN}], 1, 25000) = 1
read(21, "l\2\1\1i\0\0\0%\306\0\0-\0\0\0\6\1s\0\5\0\0\0:1.30\0\0"..., 2048) = 169
read(21, 0x83f5af8, 2048)               = -1 EAGAIN (Resource temporarily unavailable)
gettimeofday({1173245870, 225856}, NULL) = 0
writev(21, [{"l\1\0\1\0\0\0\0\266f\3\0\246\0\0\0\1\1o\0,\0\0\0/org/f"..., 184}, {"", 0}], 2) = 184
gettimeofday({1173245870, 254349}, NULL) = 0


The machine needs to have been running for a while before these issues can be seen.

mboman@mblxws01:~> uptime
  5:04pm  up  22:39,  2 users,  load average: 0.05, 1.33, 1.42


Not sure if this is related to memory leaks in this version of Slab;

mboman@mblxws01:~> rpm -qa gnome-main-menu
gnome-main-menu-0.6.3-65

mboman@mblxws01:~> ps aux|grep main-menu
mboman    3749  0.2  7.5 219004 156152 ?       S    Mar06   3:38 /usr/lib/main-menu --oaf-activate-iid=OAFIID:GNOME_MainMenu_Factory --oaf-ior-fd=21

As soon as my closest mirror stop giving me bad checksum when trying to refresh the Factory sources, I'll update to the latest version and try this again.
Comment 1 Magnus Boman 2007-09-17 22:42:04 UTC
This is still happening. If I don't kill the main-menu it will end up crashing nm-applet.
The machine needs to have been suspended for a certain amount of time (not sure what the limit is here) before this can be seen.
Comment 2 Stephan Kulow 2007-09-18 06:11:56 UTC

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