Open Bug 1314815 (dt-leak) Opened 8 years ago Updated 2 years ago

[meta] DevTools memory leaks / compartment leaks

Categories

(DevTools :: General, defect, P3)

Product:
DevTools
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
REOPENED

People

(Reporter: jryans, Unassigned)

References

(Depends on 15 open bugs, Blocks 1 open bug)

Details

(Keywords: meta)

Collecting memory / compartment leak relates issues inside the DevTools themselves.
Product: Firefox → DevTools
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Version: 49 Branch → unspecified
Depends on: 1512592
Depends on: 1539502
Depends on: 1553165
Depends on: 1476869
Depends on: 1453436
Depends on: 1439509
Depends on: 1376753
Depends on: 1084605
Depends on: 1399207
Depends on: 1358413
Depends on: 991311
Depends on: 1278731
Depends on: 1565144
Depends on: 1598239
Depends on: 1612051
Depends on: 1615426
Depends on: 1618462
Depends on: 1623191
Depends on: 1627054
Depends on: 1595797
Depends on: 1630131

Bug 1630268 showed that we very likely have memory leaks when we open and close devtools, which is a problem for the test harness that runs many tests consecutively. Alexandre provided a detailed approach to investigate in https://bugzilla.mozilla.org/show_bug.cgi?id=1630268#c25.

See Also: → https://bugzilla.mozilla.org/show_bug.cgi?id=1630268

In addition to hints provided in bug 1630268 comment 25,
I described in detail how to record memory while running mochitests:
http://techno-barje.fr/talks/2020-06-mochitest-memory/
Devin also shared to the devtools team a record of this lightning talk.
And I tried to do screenshots of what I demoed live during this talk:
https://docs.google.com/document/d/1OTfrl6j-by6g-TFgsaiXmXPxshZZgIrbOKKkeVJBd3A/edit#

Depends on: 1645325
Depends on: 1649053
Depends on: 1662241
Depends on: 1689863
Depends on: 1717897
Depends on: 1729473
Depends on: 1729925
Depends on: 1730108
Depends on: 1735024
Depends on: 1754778
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.