Bug 249132 - Dolphin incredibly slow and high memory usage when using split view.
Summary: Dolphin incredibly slow and high memory usage when using split view.
Status: RESOLVED FIXED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-26 18:10 UTC by RW
Modified: 2018-03-14 11:57 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description RW 2010-08-26 18:10:41 UTC
Version:           unspecified (using KDE 4.4.4) 
OS:                Linux

Everything is slow within dolphin when using split detail view (scrolling, right click), though this is also notable when using a single pane. Originally dolphin was set out to be a lightweight file browser, now it is heavy weight and at times unresponsive due to heavy memory usage (what does a file browser need in excess of 100mb of ram for displaying "text"?). at the moment, even the konqueror file viewer uses less memory and is faster than dolphin (weren't these shortcomings of konqueror the primary reason for developing dolphin?!).

this desperately needs cleaning up to make it properly usable on a day-to-day basis. in particular on old machines.


Reproducible: Always

Steps to Reproduce:
simply use dolphin
Comment 1 Peter Penz 2010-08-27 07:32:29 UTC
Thanks for the report, but I cannot reproduce this issue. Konqueror uses the Dolphin engine internally, so it is very strange that Konqueror does not have this problem in your environment. Probably it might be related to the following things:
- Did you enable Strigi/Nepomuk? (systemsettings -> desktop search)
- Does turning off the Information Panel or the tooltips from Dolphin help?
- Do you have enabled desktop-effects? (systemsettings -> desktop effects)
- Which widgetstyle are you using? Oxygen?
Comment 2 Julian Steinmann 2018-03-14 11:57:09 UTC
This is probably fixed with the introduction of the "new" view engine. Closing, if you still experience this bug, reopen & attach more information.