https://bugs.kde.org/show_bug.cgi?id=452585
--- Comment #7 from b...@mogwai.be --- As far as I've been able to analyze it, the issue is related to the fact that the feed updates are done in parallel. Those parallel jobs are all running on the main thread (which means that they are actually still running sequentially), but are programmed in such a way that they will give control back to the main event loop (which is handling the separate jobs and the main UI) after processing a podcast episode to ensure that the UI keeps responding. For some reason, on certain hardware/software combinations, it seems like those parallel jobs keep giving control to each other over and over again, leading to a semi-infinite loop. I really don't know what the underlying cause is and why it doesn't happen on all hardware/software combinations. I do plan to re-write the update code to use multi-threading, but it will take a while since that's not trivial. -- You are receiving this mail because: You are watching all bug changes.
