Closed
Bug 1433117
Opened 7 years ago
Closed 7 years ago
Update Debugger Frontend v11
Categories
(DevTools :: Debugger, defect)
DevTools
Debugger
Tracking
(firefox60 fixed)
RESOLVED
FIXED
Firefox 60
Tracking | Status | |
---|---|---|
firefox60 | --- | fixed |
People
(Reporter: jlast, Assigned: jlast)
References
Details
Attachments
(1 file)
(deleted),
patch
|
jdescottes
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → jlaster
Blocks: debugger-bundle-updates
Assignee | ||
Comment 1•7 years ago
|
||
Assignee | ||
Comment 2•7 years ago
|
||
Assignee | ||
Comment 3•7 years ago
|
||
Assignee | ||
Comment 4•7 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=ee065933babc8c3cc22de77e0ba483487ab1f351
^ without the reverted commits
Assignee | ||
Comment 5•7 years ago
|
||
So... the current release has some issues w/ dbg-sources on mac debug...
here is a try run of moz/central - i will re-run a bunch here as a control
https://treeherder.mozilla.org/#/jobs?repo=try&revision=8bb6fd0e6040c36be7ccb516b3cc05244d168b38
Assignee | ||
Comment 6•7 years ago
|
||
Here is 11-1 which is about the half way point between 10 and 11.
https://github.com/devtools-html/debugger.html/tree/release-11-1
https://treeherder.mozilla.org/#/jobs?repo=try&revision=fd4f2850fc17dc7f1e981498cf271560d80eefab
Assignee | ||
Comment 7•7 years ago
|
||
also worth sharing this screenshot from a failed run:
https://public-artifacts.taskcluster.net/HONdZaKCSAueRnOIuPDouA/0/public/test_info/mozilla-test-fail-screenshot_0I5tc8.png
i'm wondering if this is related to the js byte code cache issue...
Assignee | ||
Comment 8•7 years ago
|
||
Assignee | ||
Comment 9•7 years ago
|
||
a new try run sans the rtl changes
https://treeherder.mozilla.org/#/jobs?repo=try&revision=e0409c29296add0090d62c6abc78f786b4cfecfd
Assignee | ||
Comment 10•7 years ago
|
||
Attachment #8946351 -
Flags: review?(jdescottes)
Assignee | ||
Comment 11•7 years ago
|
||
Comment 12•7 years ago
|
||
Pushed by jdescottes@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/9bb00e1657e6
Update Debugger Frontend v11. r=jdescottes
Comment 13•7 years ago
|
||
Comment on attachment 8946351 [details] [diff] [review]
release-11.patch
Review of attachment 8946351 [details] [diff] [review]:
-----------------------------------------------------------------
LGTM
::: devtools/client/debugger/new/README.mozilla
@@ +2,5 @@
> See https://github.com/devtools-html/debugger.html
>
> +Version v11.0
> +Comparison: https://github.com/devtools-html/debugger.html/compare/release-10...release-11
> +Commit: https://github.com/devtools-html/debugger.html/commit/4ef9b879ef7b51430e4acdadfd24a8d7e9f64c82
I trust that this will no longer 404 after you push?
Attachment #8946351 -
Flags: review?(jdescottes) → review+
Comment 14•7 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox60:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 60
Comment 15•7 years ago
|
||
This update regressed:
* complicated.jsdebugger.open by 12%
* complicated.jsdebugger.reload by 9%
* custom.jsdebugger.open by 5%
http://firefox-dev.tools/performance-dashboard/tools/debugger.html?days=14&filterstddev=true
Flags: needinfo?(jlaster)
Comment 16•7 years ago
|
||
This translates into the debugger being significantly slower to open and reload against bild.de copy that DAMP is using.
And only slower to open against the sourcemapped example:
https://searchfox.org/mozilla-central/source/testing/talos/talos/tests/devtools/addon/content/pages/custom/debugger
(a fork of https://github.com/facebookincubator/create-react-app)
Assignee | ||
Comment 17•7 years ago
|
||
Thanks for sharing - here's a quick sheet of the commits added and my guesses on perf
https://docs.google.com/spreadsheets/d/1YYlbBKx4ZrtLjEVUciFjRSgO7WLYH8NEsEQ4MrQfqHQ/edit#gid=0
The sheet was created w/ this git script: `git log --pretty=format:"%h,%an,%s" v10.0...v11.0`
Flags: needinfo?(jlaster)
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•