Fix null pointer exception in ladspa #645
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patchset performs a number of improvements:
ladspa.rs
, at least until the fixes get upstreamed. This is to work around a new issue where pipewire appears to call the initialization functions with null pointers. This also uses a newer version ofbitvlags
internally.Rc<T>
structs between threadscargo fmt
on the repository, which hifts some things aroundWith this, I'm able to run the example locally without it crashing on Fedora 42, though there are several error messages from within ladspa.rs about being called with a NULL instance.
This closes #644