[SOLVED]Closing Dolphin after opening local ftp location = CPU to 100%

[4portswitch]

I would paste a print out but my system wont respond well enough when This occurs.

I opened Dolphin,
selected the network icon in the places side panel,
I added a network location for my ftp and named it,
the icon was created for the location within Dolphin.
I clicked the icon and browsed my files with ease WOOT! Much happiness ensued.

I closed Dolphin.

My system resources hit the top at 100% CPU usage and my whole system slowed to a crawl (of course).
I just managed to open a terminal.
After many minutes of waiting for it to come up, I ran top......minutes later,

sure enough kio-ftp had many running connections
and Dolphin was sitting there, quietly in the background, enjoying my CPU for dinner.

I attempted to kill the kio-ftp with no success.

I attempted to kill dolphin even though it shouldn't be running anyway.
It went away, as in it was no longer populating the top list.

After a few nail biting seconds the system returned to a normal state.
I rebooted the system,

I logged in and was able to get the same reaction again by opening the ftp location in Dolphin and then closing Dolphin.
I did this several times. I was able to reproduce same results every time.

I have no system errors with this and no crashes reported.
I am using the latest KDE-4 with all available updates from Synaptic.
2.6.33.6-pclos1.bfs #1 SMP PREEMPT Tue Jul 6 15:29:06 CDT 2010 i686 Intel(R) Xeon(TM) CPU 3.40GHz GNU/Linux
I do not use apt-get manually with this installation.

Would you prefer I report this to KDE folks instead of here?
Or, would you like a stab at it? mwuahahahaha.

Thanks for any assistance, I see by the list in the forums that your hands are quite full.
I greatly appreciate any time applied to this.

EDIT:    This has been solved with a work around/configuration in Dolphin(read all messages below). The solution is really not a solution. Dolphin does not handle information requests correctly when working within a local network. I have a possible reason I would like to suggest.
My guess is It attempts a "read ahead" on all the information, in every folder, of every item that is at the location your browsing and cache it. That could be an entire hard drive back up or an iso or a list of compressed items. This is because It tries to create thumbs of everything media. So instead of waiting for a request, it just goes on and on trying to read the information. The result is that when you close Dolphin it must complete the task at hand before it can stop running. Since a request for it to stop was made it gets pushed to the top of the list in importance and ends up being forced into a vicious loop by the system.
If the above is true, and I mean if, I don't think this could be fixed without a major rebuild.

[menotu]

What happens if you use Konqueror for your ftp connection?

Edit: if it occurs in Konqueror as well and this carries on you can always use Filezilla or similar as a temp measure.

[4portswitch]

Konqueror always works great. I ran several trials on it last night into this morning to verify it functions correctly.
I seem to have narrowed the problem with Dolphin a bit farther as well though still a bit out of my realm of understanding.
It would appear, after a few more attempts, that the system doesn't go to 100% right away.
It waits until the Dolphin GUI is completely gone.
Then, when the connection to the ftp should be dropped, the system instead continues to run in the background with all connections open.
Very odd indeed.
I can repeat this on one other system so far.
I can tell you that this has been happening since adopting Dolphin. Too bad I can't just remove it and reinstall it.
I have reinstalled PCLOS-2010 on this system and have gotten the same results both before the updates and after.
I made a remaster of my system before I updated so I could compare behavior.

Thanks for your quick response.


Happiness is.

[ThirdOfSix]

4portswitch,

Try going into View > Panels  in Dolphin and turn off "information" panel.

Then, also, turn off Preview in View > Previews.

This is a problem that I have had with all of the kde4 versions on my network.

I like the preview functions. But, for me they just cause too much network load and hard drive thrashing.

Every time a new version of KDE comes out, I switch back to try it then shut them off again.

This is only an issue for those of us with a number of shares on computers and NAS drives on the network. And, apparently only some of us.

[4portswitch]

Well that is interesting. I remember that I had this issue a couple of years ago with Konq. Go figure no one has addressed it since.

Thanks for the reminder, That solved it.
I wonder why it didn't turn up in the searches I attempted. I guess I just don't search key words well enough. I've never been a great search guru.
I also suppose that most people don't run ftp locally on a network and use dolphin to interact with it at the same time. Therefore the problem rarely arises.

However, I still feel that this should be considered a major bug wouldn't you agree?

After all this is supposed to be a network app and all that that implies.

Thanks again.

Happiness is.

[4portswitch]

By the way how do I mark this mostly solved? Do I simply place a comment in the subject line?

[T6]

yes, add the word (SOLVED) to the subject