https://bugs.kde.org/show_bug.cgi?id=417070
sgo...@gmail.com changed:
What|Removed |Added
CC||sgo...@gmail.com
--- Comment #21 from
https://bugs.kde.org/show_bug.cgi?id=417070
Michael K. changed:
What|Removed |Added
CC||f4tm...@web.de
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=417070
--- Comment #20 from Nate Graham ---
Yes; they both use the same KRunner runner.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417070
--- Comment #19 from Lukas Ba. ---
Is this *fixed* in the startmenu as well?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417070
Alexander Lohnau changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=417070
Lukas Ba. changed:
What|Removed |Added
CC||k...@web.de
--- Comment #17 from Lukas Ba. ---
https://bugs.kde.org/show_bug.cgi?id=417070
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=417070
Alexander Lohnau changed:
What|Removed |Added
Version Fixed In||5.20
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=417070
Alexander Lohnau changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=417070
Alexander Lohnau changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=417070
--- Comment #13 from Alex ---
This sounds good!
I currently have another patch waiting to be reviewed which improves the
overall API design of the runner plugin.
Another things that I would implement (brainstorming):
- The implementation if the
https://bugs.kde.org/show_bug.cgi?id=417070
Alex changed:
What|Removed |Added
Assignee|k...@privat.broulik.de |alexander.loh...@gmx.de
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=417070
--- Comment #12 from Hakan Bayindir ---
Hello Alex,
Thanks for the patches and all the hard work. I have a question.
As far as understood, the locking in SQLite is as follows [0]:
1. In most cases many clients can have locks on a SQLite DB.
2. If a
https://bugs.kde.org/show_bug.cgi?id=417070
--- Comment #11 from Alex ---
Edit: I just noticed the fix won't be included in Plasma 5.19, because it got
merged into master.
The commit is:
https://invent.kde.org/plasma/plasma-workspace/-/commit/61b02b16f4205d2d9b212a239fa65fe7710acc30
@broulik
https://bugs.kde.org/show_bug.cgi?id=417070
Alex changed:
What|Removed |Added
CC||alexander.loh...@gmx.de
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=417070
--- Comment #9 from Kai Uwe Broulik ---
Chrome excerts the same thing. We can still ask them I guess :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417070
--- Comment #8 from Hakan Bayindir ---
I've also tried to access the DB with SQLite browser but, it's not possible as
you've said.
Maybe we can raise the issue with Mozilla, so they can release the locking
pressure on the .sqlite files.
It looks like
https://bugs.kde.org/show_bug.cgi?id=417070
--- Comment #7 from Kai Uwe Broulik ---
So yeah, the database file is completely locked and all my queries fail while
the browser is open. Bummer :/
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417070
--- Comment #6 from Kai Uwe Broulik ---
Apparently SQLite 3 does allow concurrent connections. We only do a SELECT on
the database, no modification, so I believe this copying to a temp file isn't
necessary anymore.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=417070
Kai Uwe Broulik changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=417070
--- Comment #4 from Hakan Bayindir ---
Created attachment 125673
--> https://bugs.kde.org/attachment.cgi?id=125673=edit
Detailed KRunner activity report.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417070
--- Comment #3 from Hakan Bayindir ---
I've done the testing. You're right. Bookmarks is the culprit. Reading and
re-caching a lot of favicons and data. Creates ~100MB writes per search.
Sometimes even bigger.
I'm attaching a detailed report.
>From
https://bugs.kde.org/show_bug.cgi?id=417070
--- Comment #2 from Hakan Bayindir ---
You're welcome. Of course I can do the analysis. I think I can provide an
answer towards the end of the week.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417070
--- Comment #1 from Kai Uwe Broulik ---
Thanks for your analysis.
Can you try to figure out which plugin is causing this? E.g. try disabling all
search modules in KRunner settings and then see if you spot a pattern?
I know the Bookmarks runner does
https://bugs.kde.org/show_bug.cgi?id=417070
Hakan Bayindir changed:
What|Removed |Added
CC||ha...@bayindir.org
--
You are receiving this
25 matches
Mail list logo
