Bug #850
Corrupted epgdb crashes tvheadend
| Status: | Invalid | Start date: | 01/24/2012 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: |  Hein Rigolo | % Done: | 0% | |
| Category: | EPG | |||
| Target version: | - | |||
| Found in version: | git-fdf89b2 | Affected Versions: |
Description
Somehow my epgdb got corrupted, perhaps by running multiple instances of tvheadend at the same time.
Anyhow, the attached epgdb makes tvheadend segfault.
tvheadend2213: segfault at 0 ip 000000000041d4b9 sp 00007fff769ed790 error 4 in tvheadend[400000+1b5000]
History
#1
Updated by Hein Rigolo over 1 year ago
so you (were?) run(ning) multiple instances of tvheadend all pointing to the same config directory?
Easiest solution: don't do that ... :-)
Easiest fix: remove the epgdb file .. and restart.
Hein
#2
Updated by Peter Nevermind over 1 year ago
Already taken care of. Should not segfault anyways. =)
#3
Updated by Adam Sutton 11 months ago
- Status changed from New to Invalid
I don't think this represents a valid bug report. We could add some checksum on the file (or MD5 file etc...) just to validate the EPG database. But at this stage I'm not sure it warrants the effort given this was actually caused by running multiple instances on the same DB, which was clearly a mistake.
Adam