rlboxed soundtouch code is in libxul
Categories
(Core :: Audio/Video, defect)
Tracking
()
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...
Assignee | ||
Comment 1•1 year ago
|
||
Until we figure out how to make it happen in a LGPL-abiding way.
Comment 2•1 year ago
|
||
Set release status flags based on info from the regressing bug 1673285
Comment 3•1 year ago
•
|
||
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)
Assignee | ||
Comment 4•1 year ago
|
||
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).
Assignee | ||
Updated•1 year ago
|
Comment 6•1 year ago
|
||
Backed out changeset 763648bda75d (bug 1851107) for causing creashtest failures at rlbox_noop_sandbox.hpp
Backout: https://hg.mozilla.org/integration/autoland/rev/41426b5e88f0a0d884470ee3278183ad90da44b2
Failure log: https://treeherder.mozilla.org/logviewer?job_id=427977770&repo=autoland&lineNumber=6842
Assignee | ||
Updated•1 year ago
|
Comment 8•1 year ago
|
||
bugherder |
Comment 9•1 year ago
|
||
:glandium any follow-up expected on this?
Wondering if it should it still be leave-open?
Assignee | ||
Comment 10•1 year ago
•
|
||
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.
Updated•1 year ago
|
Description
•