Summary: | Crash program after closed tab | ||
---|---|---|---|
Product: | [Applications] akregator | Reporter: | Vladimir <curtisadmim> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | sexymimi64 |
Priority: | NOR | ||
Version: | 5.9.0 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | screen |
*** Bug 398284 has been marked as a duplicate of this bug. *** 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... *** This bug has been marked as a duplicate of bug 397866 *** |
Created attachment 114790 [details] screen 1.Open Akgregator. 2.open news 3.press View Changes Online 4. in new tab press r.click and close this tab ER: tab is closed AR: crash a program and alert on next start. destroy all history