https://bugs.kde.org/show_bug.cgi?id=387232
Simon Andric changed:
What|Removed |Added
CC||simonandr...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=387232
--- Comment #16 from Sven Brauch ---
Yeah, never mind if it wasn't intentional, happens.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387232
--- Comment #15 from RJVB ---
Well, if apologies are in order ...
Fact is I didn't realise the relationship to my patch until the report was
already submitted.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=387232
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
---
https://bugs.kde.org/show_bug.cgi?id=387232
--- Comment #8 from Milian Wolff ---
exactly, don't report bugs for crashes in your WIP patches
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387232
Kevin Funk changed:
What|Removed |Added
Resolution|FIXED |INVALID
--- Comment #13 from Kevin
https://bugs.kde.org/show_bug.cgi?id=387232
Kevin Funk changed:
What|Removed |Added
Resolution|WAITINGFORINFO |INVALID
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=387232
--- Comment #10 from Milian Wolff ---
troll answer: yes, remove the project watcher as I told you to
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387232
RJVB changed:
What|Removed |Added
Resolution|INVALID |FIXED
--- Comment #12 from RJVB
https://bugs.kde.org/show_bug.cgi?id=387232
--- Comment #9 from RJVB ---
So you can put a finger on the (supposed) bug in my patch, meaning the thing it
fails to do to avoid signals from being delivered to a stale object? Please
enlighten me if that's the case...
--
You
https://bugs.kde.org/show_bug.cgi?id=387232
RJVB changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=387232
--- Comment #11 from RJVB ---
That's a troll answer indeed (where's the flag/report thingy?). The same thing
would happen when using KDirWatch directly.
Kevin, I also feel like I'm rambling. The thing is I'm largely groping in the
https://bugs.kde.org/show_bug.cgi?id=387232
Kevin Funk changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=387232
--- Comment #6 from Kevin Funk ---
René, this bug is three hours old and it already has several pages of text. Be
assured that there are very few persons having the time/motivation to read
through all of that. I did, and it's super noisy
https://bugs.kde.org/show_bug.cgi?id=387232
--- Comment #5 from RJVB ---
So... what seems to be burning CPU is a number of FileManagerListJob instances
that keep running and calling FileManagerListJob::startNextJob() which in turn
emits the watchDir signal.
What I fail to
https://bugs.kde.org/show_bug.cgi?id=387232
--- Comment #4 from RJVB ---
There's something else that's fishy, I'm now pretty certain that the CPU
burning is due to an issue in the AbstractFileManagerPlugin and/or the
FileManagerListJob classes which somehow start reloading
https://bugs.kde.org/show_bug.cgi?id=387232
RJVB changed:
What|Removed |Added
Assignee|mp...@kde.org |kdevelop-bugs-n...@kde.org
17 matches
Mail list logo