Summary: | Dolphin and Plasma freeze for more than 5 seconds when Cut-Pasting a file | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | Alec Moskvin <alecm> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | aseigo, remy.greinhofer, s.kage |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Alec Moskvin
2009-03-07 18:22:49 UTC
works fine for me in trunk. as for dolphin freezing, I think I've seen that - file a separate report with dolphin so they can look into it. I think I can replicate what Alec is experiencing. On a desktop system with KDE 4.2.1 from ppa.launchpad.net/kubuntu-members-kde4/ubuntu with nvidia proprietary driver. When pasting a large file in dolphin (though it can be in any file browser component) plasma hangs on the kio-server progress display. Dolphin will lock up because as well, probably because of the copy/paste stuff happens in it's process. I guess this should be closed as INVALID since it's caused by the nvidia driver. But kdelibs/plasma has a design flaw here because everything is in one process, causing dolphin and plasma to lock up. > kdelibs/plasma has a design flaw here because everything is in one
> process
if the problem is that showing the dialog takes some time due to the driver, what do you suggest is the solution? put every dialog in it's own process?
there are two things that could be blocking: GPU driver related performance issues, synchronous d-bus call in progress.
if the d-bus calls are synchronous, that needs to be changed.
one possible issue i see is in kdeui/jobs/kuiserverjobtracker.cpp:
QDBusReply<QDBusObjectPath> reply = serverProxy->uiserver().requestView(componentData.aboutData()->programName(),
programIconName,
job->capabilities());
thta's a syncronous call, so if the other side isn't immediately available we'll get some blocking on both sides of the call.
Just out of curiosity, how is the Cut dialog different from the Copy dialog? Why is it that the Copy dialog does not freeze? Shouldn't it essentially be doing the same thing? I'd also like to mention that I do not experience any graphics performance issues, and that this also happens with compositing disabled. *** Bug 187944 has been marked as a duplicate of this bug. *** I repeated the steps described in the report, but I could not reproduce the behavior under KDE SC 4.3.4, Qt 4.5.3. I also tried with a file of 1.1GB, and I experienced no freeze at all. |