https://bugs.kde.org/show_bug.cgi?id=440802
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=440802
--- Comment #5 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=440802
--- Comment #4 from tagwer...@innerjoin.org ---
(In reply to irchaika from comment #3)
> Is there any way to manually trigger a situation that'd make baloo return
> the memory?
Might be worth having a look at iotop to see if it is writing to disc...
https://bugs.kde.org/show_bug.cgi?id=440802
--- Comment #3 from ircha...@airmail.cc ---
Is there any way to manually trigger a situation that'd make baloo return the
memory? something that can be used reliably without having to worry about
swapping or triggering the kernel oom
--
You are
https://bugs.kde.org/show_bug.cgi?id=440802
tagwer...@innerjoin.org changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=440802
--- Comment #1 from tagwer...@innerjoin.org ---
(In reply to irchaika from comment #0)
> It consumes nearly a gigabyte of ram despite being idle, the problem
> persists across reboots (though I haven't checked how long it takes for the
> process to
https://bugs.kde.org/show_bug.cgi?id=440802
tagwer...@innerjoin.org changed:
What|Removed |Added
CC||tagwer...@innerjoin.org
--
You are
