https://bugs.kde.org/show_bug.cgi?id=368674
--- Comment #1 from Andrius Štikonas <andr...@stikonas.eu> --- I think what happens is that output from e2fsck is stored in a variable in KPM. e2fsck keeps producing more and more output and uses more and more memory. We can already do command timeout but that will probably not work because some normal file system checks sometimes take a long time to happen, I saw one lasting about 50 minutes. One way to fix this might be to add a limit to stored output and exit with error when that limit is reached. -- You are receiving this mail because: You are watching all bug changes.
