Stop preloading Mozilla DLLs for WMF software encoding in content process
Categories
(External Software Affecting Firefox :: Other, defect)
Tracking
(firefox-esr115 unaffected, firefox-esr128 unaffected, firefox129 unaffected, firefox130+ fixed, firefox131 fixed)
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | unaffected |
firefox129 | --- | unaffected |
firefox130 | + | fixed |
firefox131 | --- | fixed |
People
(Reporter: yannis, Assigned: yannis)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
We currently preload these DLLs in all content processes, which presumably has some performance impact. We did this in bug 1910861 to mitigate the crashes with ESET from bug 1905690 - but ESET has since then pushed new changes that perhaps will fix the crashes. If not, we want to mitigate the crashes in another way that does not involve preloading the DLLs in all content processes.
Assignee | ||
Comment 1•3 months ago
|
||
We currently preload these DLLs in all content processes, which
presumably has some performance impact. We did this in bug 1910861 to
mitigate the crashes with ESET from bug 1905690 - but ESET has since
then pushed new changes that perhaps will fix the crashes. If not, we
want to mitigate the crashes in another way that does not involve
preloading the DLLs in all content processes.
Updated•3 months ago
|
Updated•3 months ago
|
Assignee | ||
Comment 2•3 months ago
|
||
As explained by :bobowen in the code review, we already allow access to the bin directory so we can actually just completely stop preloading.
Comment 3•3 months ago
|
||
Set release status flags based on info from the regressing bug 1910861
Comment 5•3 months ago
|
||
From https://bugzilla.mozilla.org/show_bug.cgi?id=1905690#c31 it sounds like you may want to request uplift to beta, but the last beta build for 130 is happening today. So if this is something you think should be in 130 beta/release, please talk with :ryanvm. It may be something to keep an eye on for the RC build or a dot release later.
Assignee | ||
Comment 6•3 months ago
|
||
We currently preload these DLLs in all content processes, which
presumably has some performance impact. We did this in bug 1910861 to
mitigate the crashes with ESET from bug 1905690 - but ESET has since
then pushed new changes that perhaps will fix the crashes. If not, we
want to mitigate the crashes in another way that does not involve
preloading the DLLs in all content processes. Preloading is not required
even with sandbox level 8, because we already allow access to the bin
dir anyway.
Original Revision: https://phabricator.services.mozilla.com/D219961
Updated•3 months ago
|
Comment 7•3 months ago
|
||
beta Uplift Approval Request
- User impact if declined: Potential performance impact at each content process startup
- Code covered by automated testing: yes
- Fix verified in Nightly: yes
- Needs manual QE test: no
- Steps to reproduce for manual QE testing: -
- Risk associated with taking this patch: Low
- Explanation of risk level: The patch restores the behavior found in versions 129 and below.
- String changes made/needed: No
- Is Android affected?: no
Assignee | ||
Comment 8•3 months ago
|
||
Thanks :lizzard, I'll see with :RyanVM.
Comment 9•3 months ago
|
||
bugherder |
Updated•3 months ago
|
Updated•3 months ago
|
Comment 10•3 months ago
|
||
uplift |
Updated•3 months ago
|
Description
•