https://bugs.kde.org/show_bug.cgi?id=342677
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sit...@kde.org
Resolution|FIXED |---
Ever confirmed|0 |1
Status|RESOLVED |REOPENED
--- Comment #4 from Harald Sitter <sit...@kde.org> ---
I can actually reproduce this. With firefox as browser and simply running
`kioclient5 exec http://networkcheck.kde.org` after a while the slave will exit
and crash during exit. What's more, I even know why. Threaded applications
shouldn't call exit() as it doesn't terminate threads so it a) breaks life time
expectations and b) runs cleanup handlers while other threads potentially are
still going about their business.
The tricky thing here of course is that we want to absolutely terminate because
of how the dispatch loop of the slaves work. So the likely only solution here
is to use quick_exit() instead, disadvantage there is that it does vastly less
cleanup.
Perhaps David has a better idea? From what I see in the code this is a tricky
problem because when the slave's exit is called we should force-terminate ASAP,
but there is no way to do that safely if multiple threads are involved.
--
You are receiving this mail because:
You are watching all bug changes.
