fix: NPE causing segmentation fault#227
fix: NPE causing segmentation fault#227ABeltramo wants to merge 2 commits intoLizardByte:nightlyfrom
Conversation
|
The flatpak failure is something I'm working on. It's an issue with CI. |
|
I was also thinking there is something odd about this. As far as I understand this is to be defined by cmake, yet there's no build instructions I've seen that define this property. What do you think? |
|
This has been introduced in 62ca9c3 I took a quick look around but, unless I'm missing something, it doesn't look like it's being set anywhere. The alternative could be that it was just used as a placeholder for when the sink or the monitor is missing so that it'll not return |
According to git blame, the change was added by #130 PR, shall we ask the owner of the PR? |
|
@Logical-sh could you give some additional insight on this? |
|
Those are not meant the be set by build or anything they are special fallback names. In pulseaudio (but not for monitor in pipewire! Otherwise that pr could have been a lot simpler) those names are special device names that resolve to the default sink/monitor by the service itself. The default string is there so if for some reason the call to get the default names fails, it attempts to use those special fallback names instead of bailing right there, instead just letting pulseaudio resolve the default devices for us. This won't work in pipewire, as the "@DEFAULT_MONITOR@" is not implemented, and to be honest if getting the default devices fails there is likely a deeper issue anyway so its not likely to really help anything to be honest, its just similar to how the old code resolved and was a nice default value for the std:strings. |
|
The problem with this PR is that we use that name later to do more work. (Setting up the fake sink and redirecting streams) |
|
After reading the ticket, there are a couple solutions here:
This would have the advantage of sunshine and anything ran on it having a set audio device inside the container to forward. (Not sure how your current audio solution works though!) |
|
Thanks @Logical-sh for the in-depth explanation, I think I understand it a little bit better now.. I think it makes sense to setup a sink on PulseAudio instead, this was likely caused by the way we run things (headless, no real audio device setup). You seem to be knowing your way around the codebase, would you be interested in helping us out understanding and documenting it better? |
|
Not that I think about it, we already setup a dummy sink, we just try to route a real sink to it, and that's what is failing. I could make a pr this weekend that fixes this null issue and lets the code still setup the dummy sink, just skipping the forwarding part. I might not remember that 100% tho, so I'll look into it and update here later! |
|
Thanks, in the meantime, I'll try to add a default sink to our PulseAudio container on GOW. Feel free to reach us on any Discord channel, I would love to chat a little bit more in depth about the codebase. I've got a few questions to ask! |
|
I'll change this to draft for now. |
|
This PR is stale because it has been open for 90 days with no activity. Comment or remove the stale label, otherwise this will be closed in 10 days. |
|
Replaced by #372 |
Update linux_build.sh
Description
PulseAudio can (and will) return
nullwhen no sink is defined, assigningnullto astd::stringwill always cause a segmentation fault.Here's a simple check before making the assignment.
Issues Fixed or Closed
Type of Change
Checklist