Define a max capacity in UntrustedModulesBackupData
Categories
(Core :: DLL Services, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox99 | --- | fixed |
People
(Reporter: toshi, Assigned: toshi)
References
Details
Attachments
(4 files)
We should limit the number of loading events stored in UntrustedModulesBackupData, otherwise the process consumes high memory if a third-party application injects their modules repeatedly as we saw in Bug 1747980.
| Assignee | ||
Comment 1•4 years ago
|
||
| Assignee | ||
Comment 2•4 years ago
|
||
This patch chnages the type of UntrustedModulesData::mEvents from
Vector to AutoCleanLinkedList. The purpose of this is for
UntrustedModulesBackupService to splice data easier and to discard
old loading events, which will be implemented in a subsequent patch.
Depends on D137244
| Assignee | ||
Comment 3•4 years ago
|
||
UntrustedModulesBackupService manages two UntrustedModulesBackupData
instances to hold third-party module loading events. We can simply have
two members instead of an array of two items, that makes the code more
readable.
Depends on D137245
| Assignee | ||
Comment 4•4 years ago
|
||
We use third-party loading events data for two purposes. One is to
send it as the third-party-modules ping. The other is to display it
on about:third-party. Currently we keep all loading events in memory,
but it may consume too much memory if modules injection happens too
often intentionally or unintentionally.
This patch is to discard old loading events after telemetry submission,
and also drops stack information after telemetry submission because
about:third-party does not use stack information.
Depends on D137246
Comment 6•4 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/c08b55356c5a
https://hg.mozilla.org/mozilla-central/rev/43a5f02b1160
https://hg.mozilla.org/mozilla-central/rev/dd59fbaa406a
https://hg.mozilla.org/mozilla-central/rev/a82e42146aed
Description
•