New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mythfrontend, mythtv-setup master: random segfaults on startup #593
Comments
I started to attempt a bisect with the first commit with the DB version 1376, which still failed, but the backtrace suggests the segfault occurs in
Returning to master, I added |
Conjecture: Since this is in the libcec close/unload functionality, #299 (or the fix applied to MythTV) may be related. |
I had seen #299 and #299 (comment) seems to work:
but that leaks memory. Without
Without CECDestroy (memory leak):
Without both it doesn't crash. This feels to me that it is memory corruption and libCEC is a red herring. I'll have to try running valgrind with a |
I'm noticing the crash as well, this is on a FreeBSD 13.2 box.
The stack trace clearly looks corrupted |
Reproduced today (but only once....) with mythtv-setup.
And this is from a debug build... |
Platform: Xubuntu 22.04
Linux scott-desktop 5.15.0-40-generic #43-Ubuntu SMP Wed Jun 15 12:54:21 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
MythTV version: master (attachments generated with MythEDID: fix out of bounds memory access #592 )
Package version: n/a (git)
Component: mythfrontend, mythtv-setup
What steps will reproduce the bug?
mythfrontend
ormythtv-setup
, no user input required.How often does it reproduce? Is there a required condition?
It appears to randomly occur about 10% of the time (without having counted).
What is the expected behaviour?
No segmentation faults terminating the process.
What do you see instead?
The screen briefly flashes with the expected menu and then the program crashes.
Additional information
I have reproduced this on my other Xubuntu 22.04 test system which uses an Intel G3258's iGPU instead of an Nvidia GTX 970. The segfaults occured with either nouveau or the Nvidia binary driver.
Valgrind revealed #592 , but I didn't see anything else relevant mythfrontend_valgrind.txt . I have not tried recompiling with
--compile-type=debug
for a clearer valgrind output.See attached logs and gdb backtraces.
I don't know what to make of the backtraces, in particular
#0 0x00007f1c3c3f2560 in ()
.mythfrontend_backtrace.3574.txt
mythfrontend_seg_fault.3574.log
mythtv-setup_backtrace.3973.txt
mythtv-setup_seg_fault.3973.log
The text was updated successfully, but these errors were encountered: