Fix a heap-based use after free during synth destruction #1730
+37
−38
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.
Previously, the sfont load was owning the
fluid_file_callbacks_t, which however might be destroyed before all sfonts using it have been destroyed.Also, if previously a new
fluid_file_callbacks_twas passed to a sfont_loader, it would have affected all previously loaded sfonts of that loader. Now, every sfont carries it's own copy offluid_file_callbacks_t.Resolves #1728
Repro:
fluidsynth some.dlsnoteon 0 60 127unload 1quitASAN report: