Closed Bug 1851107 Opened 1 year ago Closed 1 year ago

rlboxed soundtouch code is in libxul

Categories

(Core :: Audio/Video, defect)

defect

Tracking

()

RESOLVED FIXED
119 Branch
Tracking Status
firefox-esr102 --- unaffected
firefox-esr115 --- unaffected
firefox117 --- unaffected
firefox118 --- unaffected
firefox119 --- fixed

People

(Reporter: glandium, Assigned: glandium)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

I should have caught this during review in bug 1673285, but we got ourselves a big problem with soundtouch: it's LGPL. And as such we need to keep it separate from libxul. Unfortunately, that's not something that rlbox supports right now...

Until we figure out how to make it happen in a LGPL-abiding way.

Depends on: 1850640

Would the solution here be : have libsoundtouch dynamically linked (which RLBox should support fine), and would only require adjusting the moz.build settings? Or would libsoundtouch have to be dynamically loaded as well? If it needs to be dynamically loaded, I can build an RLBox wasm2c plugin which uses dlopen/dlsym pretty easily (in fact we were doing this earlier when we relied on lucet)

Flags: needinfo?(mh+mozilla)

Would the solution here be : have libsoundtouch dynamically linked (which RLBox should support fine), and would only require adjusting the moz.build settings?

At a very high level, yes. There are a bunch of subtle things that go wrong, though (like the circular dependency between libxul and liblgpglibs because of CrashReporter::AnnotateCrashReport in rlbox_wasm2c_thread_locals.cpp).

Flags: needinfo?(mh+mozilla)
Keywords: leave-open
Pushed by mh@glandium.org: https://hg.mozilla.org/integration/autoland/rev/763648bda75d Disable wasm sandboxing of libsoundtouch. r=media-playback-reviewers,karlt
Depends on: 1851694
Pushed by mh@glandium.org: https://hg.mozilla.org/integration/autoland/rev/c870f975ac3d Disable wasm sandboxing of libsoundtouch. r=media-playback-reviewers,karlt
Flags: needinfo?(mh+mozilla)

:glandium any follow-up expected on this?
Wondering if it should it still be leave-open?

Flags: needinfo?(mh+mozilla)

I was hoping what landed would be backed out by the time the freeze starts, but this is probably not going to happen, so let's keep things simple as far as release tracking is, and close this bug, since the issue as filed is fixed. I'll file a followup for what's remaining.

Status: NEW → RESOLVED
Closed: 1 year ago
Flags: needinfo?(mh+mozilla)
Keywords: leave-open
Resolution: --- → FIXED
Blocks: 1853840
Target Milestone: --- → 119 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: