Opened 15 years ago
Closed 14 years ago
Last modified 14 years ago
#7345 closed defect (invalid)
Memory corruption in mythbackend after failed recording of HD-PVR
Reported by: | Owned by: | danielk | |
---|---|---|---|
Priority: | minor | Milestone: | unknown |
Component: | MythTV - Recording | Version: | head |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
Either the HD-PVR is not configured properly in myth or the v4l driver has a problem coexisting between the HD-PVR and the HVR-1800 in the same computer (guess). After completing a failed recording attempt on /dev/video0, the backend faults with a malloc error (memory corruption).
MythTV Version : 22481 MythTV Branch : trunk Network Protocol : 50 Library API : 0.22.20091014-1 QT Version : 4.5.0 Options compiled in:
linux release using_oss using_alsa using_backend using_directfb using_dvb using_firewire using_frontend using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu using_libfftw3 using_lirc using_mheg using_opengl_video using_opengl_vsync using_qtwebkit using_v4l using_x11 using_xrandr using_xv using_xvmc using_xvmc_vld using_xvmcw using_bindings_perl using_bindings_python using_opengl using_vdpau using_ffmpeg_threads using_libavc_5_3 using_live using_mheg
Attachments (2)
Change History (5)
Changed 15 years ago by
Attachment: | mythbackend.log.1 added |
---|
Changed 15 years ago by
Attachment: | messages.txt added |
---|
comment:1 Changed 14 years ago by
Component: | MythTV - General → MythTV - Recording |
---|---|
Owner: | changed from Isaac Richards to danielk |
comment:2 Changed 14 years ago by
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:3 Changed 14 years ago by
FWIW, I just experienced this crash in 0.23 (25145) a few minutes ago (and apparently last night as well). I've restarted the backend under valgrind. I'll let you know if/when I get another crash.
For any memory corruption please attach a valgrind log.
I'm closing this ticket only because of it's age. If you can reproduce with 0.23, please open a new ticket with the valgrind log in addition to the backend log.