Unused methods exist around value grips
Categories
(DevTools :: Debugger, task)
Tracking
(firefox133 fixed)
| Tracking | Status | |
|---|---|---|
| firefox133 | --- | fixed |
People
(Reporter: ochameau, Assigned: ochameau)
References
(Blocks 1 open bug)
Details
Attachments
(8 files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review |
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
| Assignee | ||
Comment 2•1 year ago
|
||
This was only used in test and was involving the promote hooks method.
| Assignee | ||
Comment 3•1 year ago
|
||
I kept the method on the front as many xpcshell test rely on this to simply
instantiate a front and it is tedious to create an object front via DevToolsClient.createObjectFront.
| Assignee | ||
Comment 4•1 year ago
|
||
(getParent() was equal to the thread actor)
| Assignee | ||
Comment 5•1 year ago
|
||
It sounds safer and easier to always check if the thread is paused
and _pausePool is defined to register the object actor in the right pool.
| Assignee | ||
Comment 6•1 year ago
|
||
| Assignee | ||
Comment 7•1 year ago
|
||
The actor objects usualy receive a connection as first argument
and thread attribute isn't used in hooks.
| Assignee | ||
Comment 8•1 year ago
|
||
| Assignee | ||
Comment 9•1 year ago
|
||
It's condition was the opposite of its meaning...
and it is only used within the class, so no need to expose it on hooks.
Comment 10•1 year ago
|
||
Comment 11•1 year ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/985b7383feaa
https://hg.mozilla.org/mozilla-central/rev/a95a3f0ebccd
https://hg.mozilla.org/mozilla-central/rev/0a821ddf28a1
https://hg.mozilla.org/mozilla-central/rev/d8faa541e2ad
https://hg.mozilla.org/mozilla-central/rev/70bf92d8c197
https://hg.mozilla.org/mozilla-central/rev/fe5f26df8632
https://hg.mozilla.org/mozilla-central/rev/b52f4af8feeb
https://hg.mozilla.org/mozilla-central/rev/bfa6b93cf1c5
Perfherder has detected a devtools performance change from push 6d1113bb77a8bd300a5136c427d49bd55c64902f.
Improvements:
| Ratio | Test | Platform | Options | Absolute values (old vs new) |
|---|---|---|---|---|
| 7% | damp console.log-in-loop-content-process-document | windows11-64-shippable-qr | e10s fission stylo webrender | 83.85 -> 77.61 |
| 6% | damp console.log-in-loop-content-process-document | linux1804-64-shippable-qr | e10s fission stylo webrender | 270.49 -> 253.88 |
| 5% | damp console.log-in-loop-content-process-document | macosx1015-64-shippable-qr | e10s fission stylo webrender | 225.54 -> 214.32 |
| 3% | damp console.log-in-loop-content-process-window | windows11-64-shippable-qr | e10s fission stylo webrender | 248.68 -> 240.38 |
Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.
If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.
You can run these tests on try with ./mach try perf --alert 2329
For more information on performance sheriffing please see our FAQ.
Description
•