https://bugs.kde.org/show_bug.cgi?id=472862
--- Comment #23 from Harald Sitter <sit...@kde.org> --- Git commit 2fc44a3c300324c614f2d3b86fb465f2c413c70c by Harald Sitter. Committed on 03/11/2023 at 13:25. Pushed by sitter into branch 'master'. kdirwatch: don't crash after moving threads if a user moves a public watch instance across threads we used to have a d but now local data (thereby not running the dtor) and so eventually the private watch in the old thread would try to emit data into a since deleted public watch in the new thread to prevent this problem we'll "brick" the watch upon moving threads. specifically we'll fully unregister it with the old private and create/apply a new private in the new thread. since we currently have no way to reliably copy Entry as part of this we cannot really replicate the correct watches on the new thread. definitely something that could be made to work in the future though. in the meantime critically log that moving threads does not do what you expect it to do when used with kdirwatch. M +30 -0 autotests/kdirwatch_unittest.cpp M +30 -0 src/lib/io/kdirwatch.cpp M +5 -0 src/lib/io/kdirwatch.h https://invent.kde.org/frameworks/kcoreaddons/-/commit/2fc44a3c300324c614f2d3b86fb465f2c413c70c -- You are receiving this mail because: You are watching all bug changes.
