https://bugs.kde.org/show_bug.cgi?id=392133
--- Comment #36 from Nikita Melnichenko <nikita+...@melnichenko.name> --- (In reply to PhobosK from comment #35) > Sorry but this still happens for me on KF5 5.78 and Plasma 5.20.5 and Apps > 20.12.1 I think yours is a different issue. You mentioned it happens with network fs only. It's not exactly "doing nothing" like in Piotr's or David's cases. ;) Nevertheless, I can still help if you provide debug tool output. > It is hard for me to debug because it needs some time Krusader to run (like > some 4-6 ours of use) and use it. There is no need to debug from your side, just follow these simple steps: 1. emerge heaptrack (needs unmasking). 2. In console run "heaptrack krusader" and use it as normal for a while until you experience 1+ Gb of memory allocated. Unlike valgrind, perf loss is only about 10-15%. 3. Share the heaptrack.krusader.xxxx.gz file via some file sharing service like gdrive. It contains backtraces for all the allocations happened during the run, so we can track down what's the memory is used for. -- You are receiving this mail because: You are watching all bug changes.
