Opened 10 years ago
Closed 10 years ago
Last modified 10 years ago
#9387 closed Bug Report (fixed)
Mythfrontend segfaults
| Reported by: | Owned by: | paulh | |
|---|---|---|---|
| Priority: | blocker | Milestone: | 0.25 |
| Component: | MythTV - General | Version: | Master Head |
| Severity: | high | Keywords: | |
| Cc: | Ticket locked: | no |
Description
I've started to see frontend segfaults in different places within last couple of days or week. Segfaults happen in MythNews?, MythBrowser? and in playback startup. There are couple of backtraces attached.
Attachments (5)
Change History (11)
Changed 10 years ago by
| Attachment: | mythversion.txt added |
|---|
Changed 10 years ago by
| Attachment: | mythnews-bt.txt added |
|---|
Changed 10 years ago by
| Attachment: | mythnews-bt2.txt added |
|---|
Changed 10 years ago by
| Attachment: | mythbrowser-bt.txt added |
|---|
comment:1 Changed 10 years ago by
Changed 10 years ago by
| Attachment: | playbackbox-bt.txt added |
|---|
comment:2 Changed 10 years ago by
Your version info indicates that you have custom patches in your tree.
1) please use unpatched source from git and test again
2) please be sure to "make distclean" before compiling. There have been several API changes recently.
comment:3 Changed 10 years ago by
| Milestone: | unknown → 0.25 |
|---|---|
| Owner: | set to beirdo |
| Priority: | minor → blocker |
| Severity: | medium → high |
| Status: | new → assigned |
Gavin, I can confirm this bug so we don't need Otto to follow those steps this time.
For me it seems to be directly related to the browser widget. e.g. Shortly after viewing the program details screen the frontend crashes. There is enough of a lag that it can appear that the trigger was another action which might explain Otto seeing the problem on starting playback. The mythnews/mythbrowser links are obvious. This doesn't mean that it's the browser itself, but something has changed recently that causes events originating from this widget to trigger a segfault.
comment:4 Changed 10 years ago by
| Owner: | changed from beirdo to paulh |
|---|
comment:5 Changed 10 years ago by
| Resolution: | → Fixed |
|---|---|
| Status: | assigned → closed |
In ([444c43f3b])
Fix a seg fault caused by not removing the BrowserApi? from the list of listeners when its destructed.
Fixes ticket 9387.
comment:6 Changed 10 years ago by
| Resolution: | Fixed → fixed |
|---|
Fix a seg fault caused by not removing the BrowserApi? from the list of listeners when its destructed.
Fixes ticket 9387.
Changeset: 444c43f3be201bc347e856039422f35677747a5b
Another crash happened (bt attached) and now within Watch Recordings -screen. It looks from the backtraces that it's always related to MythCoreContext? / MythObservable? / sending events, even though happening in lots of places and screens.