-
Notifications
You must be signed in to change notification settings - Fork 50
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
Possible FreeDV crash when adjusting audio settings with pavucontrol #418
Comments
I have just tried the very same thing, this used to work in the past and now I get a segfault, here is gdb's output when it happened, seems to be a threading issue in StartRxStream where it's trying to change the soundcard out name: PulseAudioDevice[Tue Jun 6 19:32:52 2023]: stream named alsa_output.usb-Generic_Realtek_USB2.0_Audio-00.analog-stereo has been moved to alsa_output.usb-1130_USB_AUDIO-00.analog-stereo Thread 1 "FreeDV GUI" received signal SIGSEGV, Segmentation fault. Thread 66 (Thread 0x7fffa97fa6c0 (LWP 257812) "FreeDV GUI"): Thread 65 (Thread 0x7fffa9ffb6c0 (LWP 257811) "FreeDV GUI"): Thread 64 (Thread 0x7fffaa7fc6c0 (LWP 257810) "FreeDV GUI"): Thread 63 (Thread 0x7fffaaffd6c0 (LWP 257809) "FreeDV GUI"): Thread 62 (Thread 0x7fffab7fe6c0 (LWP 257808) "FreeDV PS"): Thread 61 (Thread 0x7fffabfff6c0 (LWP 257807) "FreeDV PS"): Thread 60 (Thread 0x7fffb8ff96c0 (LWP 257806) "FreeDV PS"): Thread 59 (Thread 0x7fffb97fa6c0 (LWP 257805) "FreeDV PS"): Thread 58 (Thread 0x7fffb9ffb6c0 (LWP 257804) "FreeDV PS"): Thread 57 (Thread 0x7fffba7fc6c0 (LWP 257803) "FreeDV PS"): Thread 56 (Thread 0x7fffbaffd6c0 (LWP 257802) "FreeDV PAOut"): Thread 55 (Thread 0x7fffbb7fe6c0 (LWP 257801) "FreeDV rxThread"): Thread 54 (Thread 0x7fffbbfff6c0 (LWP 257800) "FreeDV PAOut"): Thread 53 (Thread 0x7fffddffb6c0 (LWP 257799) "FreeDV txThread"): Thread 52 (Thread 0x7fffde7fc6c0 (LWP 257798) "threaded-ml"): Thread 6 (Thread 0x7fffdeffd6c0 (LWP 257733) "dconf worker"): Thread 5 (Thread 0x7fffdf7fe6c0 (LWP 257732) "gdbus"): Thread 3 (Thread 0x7fffe4bfe6c0 (LWP 257730) "gmain"): Thread 2 (Thread 0x7fffe53ff6c0 (LWP 257729) "pool-spawner"): Thread 1 (Thread 0x7ffff2b21fc0 (LWP 257726) "FreeDV GUI"): |
I have the same problem with frequency reported as 0Hz to FreeDV Reporter. Sometimes it works, sometimes it doesn't. Toggling Stop/Start usually updates the web page with correct frequency. Updating the report frequency box manually, or selecting a predefined frequency in the menu works too. Like LU3JIJ, I'm not using CAT so my radio is never polled via hamlib. I'm using FreeDV v1.8.10.1 on win10 at the moment. |
Thanks for the stack trace, @Tyrbiter. Based on it it looks like something changed since the feature was written that's causing memory to go out of scope. Should be a straightforward fix, let me try something real quick. |
@JohBod, I took a brief look and it looks like it should be working, even without hamlib turned on. I'll have to investigate more tonight (not at home). |
@tmiw, I have seen many stations reporting 0Hz on the web page and I suspect that some of these zeroes were caused by this elusive bug. The path from the "Report Frequency" box to the web page is quite long, maybe the problem is not in the FreeDV-GUI code? |
It should be possible to capture the network packets using Wireshark, that would definitively identify if freedv-gui is sending 0 or not. |
With Hamlib disabled, I can duplicate the issue @JohBod described but it's very much intermittent; I need to push Start/Stop multiple times for it to happen. I'll tweak some stuff to hopefully help. |
With the changes in #421, I didn't notice 0 MHz being reported after repeatedly connecting and disconnecting 20+ times in a row. (Previously it was happening maybe once every 3-5 connections.) Let me know if that works better for you guys as well. |
From FreeDV Reporter earlier:
The text was updated successfully, but these errors were encountered: