https://bugs.kde.org/show_bug.cgi?id=392133
Nikita Melnichenko <nikita+...@melnichenko.name> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Memory leak (2.6.0 – 2.7.0) |Huge memory consumption
| |while doing nothing
Resolution|--- |WAITINGFORINFO
Component|krarc |general
Status|REOPENED |NEEDSINFO
Severity|normal |major
Version|2.6.0 |2.7.0
--- Comment #11 from Nikita Melnichenko <nikita+...@melnichenko.name> ---
Thanks for reaching back after trying on the latest stable. This is very weird
issue since nobody else experience anything similar.
Since valgrind is not showing leaks, it's most likely not a leak. Krusader
allocates resources for something it needs. Question is, what does it need?
Could you please run `krusader -d` in the same setting (fresh user, tabs at
'/') and attach here?
Another thing to try is `strace krusader` but the output might be big.
I assume you know how to redirect stdout and stderr to file (2>&1 >file).
--
You are receiving this mail because:
You are watching all bug changes.
