https://bugs.kde.org/show_bug.cgi?id=470382
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=470382
--- Comment #11 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=470382
--- Comment #10 from tagwer...@innerjoin.org ---
(In reply to Ovear from comment #9)
> Memory: 584.4M (high: 512.0M available: 0B peak: 584.9M)
You can see Baloo is pushing at the limit, the system has given it a bit of
leeway but it not going to ca
https://bugs.kde.org/show_bug.cgi?id=470382
--- Comment #9 from Ovear ---
Hi,
I have done some tests of this situation.
> I think I'd stepwise reduce the MemoryHigh value rather than removing the
> override.
Thanks for your suggestion, and you predicted exactly what will happen next.
First, t
https://bugs.kde.org/show_bug.cgi?id=470382
--- Comment #8 from tagwer...@innerjoin.org ---
(In reply to Ovear from comment #7)
> Memory: 12.0G (high: 31.2G available: 5.2G peak: 13.2G) > Limit to 50% by
> override.conf :-/
Maybe the rest of the system is not asking for memory so Baloo is no
https://bugs.kde.org/show_bug.cgi?id=470382
--- Comment #7 from Ovear ---
Hi,
Thanks for the update! I hadn't noticed that this problem was fixed. I'll
remove the overridden settings to see if kde-baloo works as expected.
For now, here's a brief update on the current memory usage, which I'm not
https://bugs.kde.org/show_bug.cgi?id=470382
tagwer...@innerjoin.org changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=470382
tagwer...@innerjoin.org changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=470382
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=470382
--- Comment #5 from tagwer...@innerjoin.org ---
(In reply to tagwerk19 from comment #4)
> ... There's a wonderful, eye watering
> example in Bug 394759 (scroll down to the 13th comment) ...
Sorry that should be:
https://bugs.kde.org/show_bug.cgi?id=3
https://bugs.kde.org/show_bug.cgi?id=470382
--- Comment #4 from tagwer...@innerjoin.org ---
> ... change MemoryHigh works for me. According to status output from systemd,
> baloo just hits the memory limited by systemd ...
That was a lucky guess then :-)
> Is that possible to output a warning whe
https://bugs.kde.org/show_bug.cgi?id=470382
--- Comment #3 from Ovear ---
Sorry for the typo.
> Except that, is that possible to find what file / reason it wants to index
> that caused those high memory demand?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470382
Ovear changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=470382
tagwer...@innerjoin.org changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=470382
Ben Bonacci changed:
What|Removed |Added
CC||b...@benbonacci.com
Component|general
15 matches
Mail list logo