https://bugs.kde.org/show_bug.cgi?id=387232
RJVB <rjvber...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|INVALID |FIXED
--- Comment #12 from RJVB <rjvber...@gmail.com> ---
Got rid of the watchDir signal and let the addDir() call be made directly by
the FileManagerListJob.
That solves the direct reason for the crash (no more signals, so none delivered
to a stale object either).
However, the underlying issue must persist and has nothing to do with my patch.
The CPU burning should have been a clear signal: the entire project is being
reloaded repeatedly because files keep changing in the project root. And as far
as I can see there is no protection whatsoever against doing multiple
concurrent reloads; FileManagerListJob happily runs as many copies of itself as
requested.
--
You are receiving this mail because:
You are watching all bug changes.
