Opened 11 years ago
Closed 11 years ago
#12370 closed Bug Report - Crash (Unverified)
QTCore SIGSEV Crash - Mythbackend
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | major | Milestone: | unknown |
| Component: | MythTV - General | Version: | 0.27.4 |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
After being stable for several weeks, I encountered the same Mythbackend crash twice this week. Running from command line with log level debug.
Attachments (4)
Change History (6)
by , 11 years ago
| Attachment: | mythbackend-log.txt.zip added |
|---|
by , 11 years ago
| Attachment: | mythbackend-version.txt added |
|---|
by , 11 years ago
| Attachment: | mythbackend-crash1.txt added |
|---|
by , 11 years ago
| Attachment: | mythbackend-crash2.txt added |
|---|
comment:1 by , 11 years ago
comment:2 by , 11 years ago
| Resolution: | → Unverified |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
The crash seems to have occurred deep in QT, in a way that would seem unrelated to our code.
There are two possibilities, an update to QT introduced a bug or there was a memory corruption issue - either caused by software or hardware. Either way there's just not enough information to go on.
If it has been stable for weeks then sudden instability would point to factors outside our control.
I would however suggest you upgrade to the latest version of 0.27.4, since it appears you are running a version which includes a known bug with UPnP - hence all the SSDP warnings in the log. I would also suggest you don't habitually run with debug level logging, it can have a significant impact on system performance.