Opened 13 years ago
Closed 13 years ago
#10405 closed Bug Report - Crash (Fixed)
segfault on SB between b85f5bb and 7b526c4
Reported by: | Owned by: | Raymond Wagner | |
---|---|---|---|
Priority: | blocker | Milestone: | 0.25 |
Component: | MythTV - General | Version: | Master Head |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
The mythbackend program segfaults on the slave backend. MB runs ok. The SB complained that the frequency of a channel was out of bounds, but I've not scanned for any channels for a week or so.
I am attaching backend log and debug log.
MythTV Version : v0.25pre-4799-g7b526c4-dirty MythTV Branch : master Network Protocol : 72 Library API : 0.25.20120304-1 QT Version : 4.7.2 Options compiled in: linux debug use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_dvb using_frontend using_hdpvr using_iptv using_ivtv using_libcrypto using_libfftw3 using_libxml2 using_libudf using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_v4l1 using_x11 using_xrandr using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vdpau using_ffmpeg_threads using_live using_mheg using_libxml2 using_libudf
Attachments (3)
Change History (15)
comment:1 Changed 13 years ago by
comment:2 Changed 13 years ago by
Milestone: | unknown → 0.25 |
---|---|
Owner: | set to Raymond Wagner |
Priority: | minor → blocker |
Status: | new → assigned |
Type: | Bug Report - General → Bug Report - Crash |
Changed 13 years ago by
Attachment: | backend.log added |
---|
comment:3 Changed 13 years ago by
Status: | assigned → accepted |
---|
No sense making things difficult when it's under the 256KB limit.
comment:4 Changed 13 years ago by
What distro are you using? Is this segfault occurring immediately after startup, or any time you try to run mythbackend?
comment:5 Changed 13 years ago by
Status: | accepted → infoneeded |
---|
comment:6 Changed 13 years ago by
openSuSe 11.4 is the SB that excibits the problem. The MB is on 12.1. The segfault occurs immediately after starting mythbackend, either through the startup script or by calling it directly.
comment:7 Changed 13 years ago by
Status: | infoneeded → assigned |
---|
Changed 13 years ago by
Attachment: | readyRead.txt added |
---|
BT of frontend crash. Looks like a tear-down order problem.
comment:8 Changed 13 years ago by
Use deleteLater() when deleting server sockets in ServerPool?.
Use Qt's deleteLater() rather than delete when deleting sockets, so the actual delete is deferred until reached by the event loop. This removes one potential avenue for null referencing causing segfaults on teardown.
Refs #10405
Branch: master Changeset: 65196663982e3a8b510d8403988000a325d6f130
comment:9 Changed 13 years ago by
MythTV Version : v0.25-beta-18-gcf9ee65-dirty
It's running ok now. Please close this ticket as fixed.
Best regards,
Yianni.
comment:11 Changed 13 years ago by
Ok, I think I maybe confused the issue:
Both tickets are now fixed, and both were fixed by the commits you made.
Both problems were occuring on the same pc, but this ticket was affecting the backend part whereas #10418 the frontend (backend was working ok).
Both starting occuring at the commits I mentioned.
I can provide any log you require, but both tickets are fixed now for me, i.e. both frontend and backend start and stop normally on this pc.
Regards,
Yianni.
comment:12 Changed 13 years ago by
Resolution: | → Fixed |
---|---|
Status: | infoneeded → closed |
Closing due to user report that it is fixed.
The actual commit that causes the segfault is f5aa5e8. Up and including b6f9e1d mythbackend starts normally.
This problem only affects the slave backend, the MB runs normally, Frontends are not affected.
Any more info I should provide?
Yianni.