This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Run dialog (Alt+F2) some time delays to display it self.

Tags: None
(comma "," separated)
firewalker
Registered Member
Posts
67
Karma
0
OS
Hello.

Since KDE-4.10.x there is a big delay between issuing the Run Command... and displaying the Run Command... dialog. This apply using Alt+F2, Kmenu > Run Command... and Dbus call. Have anyone else noticed it?

Example:
time qdbus org.kde.krunner /App display

real 0m7.809s
user 0m0.010s
sys 0m0.010s

Eight seconds. It seems it's a;ways around 7~8 seconds.

After the initial delay if I launch it again it displays it instantly. After some time (minutes) it will delay again. Also I haven't noticed any high CPU usage during the delay.

Anyone else faces this behavior?

Extra infos:

kde4-config --version:
Qt: 4.8.4
KDE Development Platform: 4.10.1
kde4-config: 1.0

GPU:
VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
SandyBridge architecture Core i3-2350M + HD 3000 (shared memory)

Effects enabled.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Hm, I have never seen this behaviour before (and cannot reproduce it at the moment).
One thing I can think of is that it is getting swapped off by your system (which would explain why it is okay once you have opened it up, but lags after a few hours).

Can you please check your system memory usage, using a application such as htop?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
firewalker
Registered Member
Posts
67
Karma
0
OS
I can't see any memory usage change when this happens. I also monitored krunner individually for CPU and Memory usage without noticing "spikes".

time qdbus org.kde.krunner /App display


real 0m4.419s
user 0m0.007s
sys 0m0.010s

free -m -t -o
total used free shared buffers cached
Mem: 3430 2498 932 0 45 1727
Swap: 5119 0 5119
Total: 8550 2498 6052


sudo iotop -o -b|grep krunner

TID PRIO USER DISK READ DISK WRITE SWAPIN IO COMMAND
1899 be/4 firewalk 8.13 M/s 19.54 M/s 0.00 % 83.20 % kdeinit4: krunner [kdeinit]
4259 be/4 firewalk 69.69 K/s 0.00 B/s 0.00 % 1.47 % qdbus org.kde.krunner /App display
1899 be/4 firewalk 708.51 K/s 7.41 M/s 0.00 % 74.01 % kdeinit4: krunner [kdeinit]
1899 be/4 firewalk 1401.55 K/s 6.38 M/s 0.00 % 99.99 % kdeinit4: krunner [kdeinit]
1899 be/4 firewalk 3.52 M/s 24.54 M/s 0.00 % 76.96 % kdeinit4: krunner [kdeinit]
1899 be/4 firewalk 3.85 K/s 0.00 B/s 0.00 % 16.94 % kdeinit4: krunner [kdeinit]
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Hm, unusual. Have you tried disabling runners which you do not use / use infrequently to try to alleviate the problem?
I would recommend logging out and back in again after making such configuration changes to ensure it has kicked in.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
firewalker
Registered Member
Posts
67
Karma
0
OS
Yes, disabling runners I don't use really helped. Thanks.


Bookmarks



Who is online

Registered users: bancha, Bing [Bot], Evergrowing, Google [Bot], lockheed, mesutakcan, Sogou [Bot]