https://bugs.kde.org/show_bug.cgi?id=398283
Michael <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Michael <[email protected]> --- I'm not entirely sure this is the same bug, but it sounds like it. I've got two scenarios that trigger it: 1. Open Akregator 2. Open two articles, the second of which must be unread 3. Close the last tab 4. Akregator crashed Otherwise: 1. Open Akregator 2. Open an article 3. Close the tab 4. Click on any other article 5. Akregator crashed In the first scenario, you can get a backtrace that leads us to FrameManager::slotRemoveFrame (the `delete frame` line). None of this happens when the `delete frame` line is commented. I'm guessing a child of the Frame object might still be in use in another thread, but I don't really where to look now... -- You are receiving this mail because: You are the assignee for the bug.
