Opened 10 years ago
Closed 6 years ago
#12199 closed Bug Report - General (Won't Fix)
Invalid file requested when scrolling quickly through recordings list
Reported by: | stuartm | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 0.27.7 |
Component: | MythTV - General | Version: | Master Head |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
Can reproduce this one fairly reliably, seems to help if the frontend hasn't cached the preview images. The segfault is always preceeded with lines suggesting that the backend was asked to open a completely invalid url, not yet sure where this is coming from. It obviously shouldn't be segfaulting though.
2014-07-05 10:09:26.031192 E FileRingBuf(//home/gbee/tmp//home/gbee/tmp): OpenFile(): Could not open. 2014-07-05 10:09:26.035760 E MainServer: Can't open //home/gbee/tmp//home/gbee/tmp 2014-07-05 10:09:26.036288 W MainServer: Unknown socket closing MythSocket(0x299a480)
Attachments (1)
Change History (7)
Changed 10 years ago by
Attachment: | backtrace.txt added |
---|
comment:1 Changed 10 years ago by
Priority: | blocker → major |
---|---|
Severity: | high → medium |
Summary: | Backend segfault when paging/scrolling quickly through recordings list → Invalid file requested when scrolling quickly through recordings list |
Type: | Bug Report - Crash → Bug Report - General |
The seems to be the one already fixed in [98bec5c8]. Leaving just the question of how the backend comes to be requesting such an obviously bad file path.
comment:2 Changed 10 years ago by
Can you reproduce that one in 0.27 or master only?
A bit confused with the milestone
comment:3 Changed 10 years ago by
Master only, I've not tried 0.27. The milestone reflects the earliest version at fix will go into, assuming it proves to be an issue in 0.27 as well. 'Version' reflects the latest version in which the bug was found.
comment:4 Changed 9 years ago by
Milestone: | 0.27.4 → 0.27.6 |
---|
comment:5 Changed 8 years ago by
Milestone: | 0.27.6 → 0.27.7 |
---|
Reschedule all tickets planned for, but not solved in time for, 0.27.6 to 0.27.7.
comment:6 Changed 6 years ago by
Resolution: | → Won't Fix |
---|---|
Status: | new → closed |
Closing any remaining open tickets for 0.27
If the issue still persists, feel free to reopen and align to a current release (v29 or master)
Full Backtrace