Bug 398283 - Crash program after closed tab
Summary: Crash program after closed tab
Status: RESOLVED DUPLICATE of bug 397866
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 5.9.0
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-05 08:07 UTC by Vladimir
Modified: 2018-11-20 11:56 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
screen (49.02 KB, image/png)
2018-09-05 08:07 UTC, Vladimir 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir 2018-09-05 08:07:50 UTC 
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
Comment 1 Andrew Crouthamel 2018-09-05 14:31:32 UTC 
*** Bug 398284 has been marked as a duplicate of this bug. ***
Comment 2 Michael 2018-10-24 17:03:35 UTC 
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...
Comment 3 Christoph Feck 2018-11-20 11:56:42 UTC 

*** This bug has been marked as a duplicate of bug 397866 ***