I just have a quite strange issue in KDE 4.7.4 on Ubuntu.

Dolphin reacts extremely slowly when trying to navigate somewhere (in home dir).
I click something and it will react after 10 seconds or so.
The system is idle. If I do ls -l on the same dir in terminal, the response is immediate. If I open nautilus at the same time and browser there, the response is also instant. Only KDE-programs and Eclipse seem to be affected.

I like KDE so much, but somehow it doesn't like me...

only home directory? if so is home dir huge or unusual in anyway?

google01103 wrote:only home directory? if so is home dir huge or unusual in anyway?

I didn't try with anything outside home, but I'm quite sure that wouldn't have made any difference.

No, there's nothing unusual with my home.

After reboot, the issue disappeared.
Since Eclipse also had the same symptoms, I suspect an underlying service somehow broke. Any idea what I should check if that happens again?

if cpu open ksysguard and check cpu usage

if i/o check with iotop or by adding i/o read and write columns to ksysguard (right click any column header and select the additional metric)

KDE 4.7.4 on Gentoo

Same problem here, not only in home. The problem exist the whole system. Then about 2 Days it's ok, then dolphin freeze again... after about 15 minutes, it works normally again. It's always the same, freeze, not freeze, freeze, not freeze.

This is also at the same time in konqueror, when you browse local files. At this time the system is idle.

Greetings
boospy

Is there a way to attach a profiler to a running process? Otherwise it will be hard to analyze such an issue (knowing no way to reproduce it)

didi_X8 wrote:Is there a way to attach a profiler to a running process? Otherwise it will be hard to analyze such an issue (knowing no way to reproduce it)

I don't think it's possible for valgrind.
You could run it in a debugger, which is way faster; then you could try to Ctrl+C it as soon as it hangs.

Once it freezes, you should be able to attach GDB using the --pid option of GDB.

Solved the problem. I had two same NFS-share lines in the fstab

Greetings
boospy