Closed
Bug 936143
Opened 12 years ago
Closed 12 years ago
Fix js_GetScriptLineExtent. (r=?)
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla28
People
(Reporter: shu, Assigned: shu)
Details
(Whiteboard: [qa-])
Attachments
(4 files, 1 obsolete file)
2.62 KB,
patch
|
jimb
:
review+
|
Details | Diff | Splinter Review |
1.52 KB,
patch
|
shu
:
review+
|
Details | Diff | Splinter Review |
1.99 KB,
patch
|
lsblakk
:
approval-mozilla-aurora+
lsblakk
:
approval-mozilla-beta-
|
Details | Diff | Splinter Review |
1.77 KB,
patch
|
lsblakk
:
approval-mozilla-aurora+
lsblakk
:
approval-mozilla-beta-
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Comment 1•12 years ago
|
||
This is crazy, js_GetScriptLineExtent has been incorrect for ages AFAICT, for
sequences of source notes where, for N > M,
setline N
setline M
newline
When processing setline M, it stops counting newlines because M <= N, so if the
script ends on source notes, it can give back a short line extent. Test
forthcoming.
Attachment #828839 -
Flags: review?(jimb)
Assignee | ||
Updated•12 years ago
|
Attachment #828839 -
Attachment is obsolete: true
Attachment #828839 -
Flags: review?(jimb)
Assignee | ||
Comment 3•12 years ago
|
||
> script ends on source notes, it can give back a short line extent.
I meant to say if the script ends on newline source notes.
Comment 4•12 years ago
|
||
Comment on attachment 828864 [details] [diff] [review]
Fix js_GetScriptLineExtent. (r=?)
Review of attachment 828864 [details] [diff] [review]:
-----------------------------------------------------------------
::: js/src/jit-test/tests/debug/Script-startLine.js
@@ +44,5 @@
> test(g.f2);
> test(g.f2);
> +
> +// Having a last = Error().lineNumber forces a setline srcnote, so test a
> +// function that ends with of newline srcnotes.
"ends with of"???
Attachment #828864 -
Flags: review?(jimb) → review+
Comment 5•12 years ago
|
||
But why not just take out all that hair, while we're here?
Assignee | ||
Updated•12 years ago
|
Attachment #828881 -
Flags: review+
Assignee | ||
Comment 6•12 years ago
|
||
Backed out as part of https://hg.mozilla.org/integration/mozilla-inbound/rev/67f5d934127c because something in the push caused various test bustage on Linux ASAN's browser-chrome suite:
https://tbpl.mozilla.org/php/getParsedLog.php?id=30444281&tree=Mozilla-Inbound
https://tbpl.mozilla.org/php/getParsedLog.php?id=30444457&tree=Mozilla-Inbound
https://tbpl.mozilla.org/php/getParsedLog.php?id=30445445&tree=Mozilla-Inbound
https://tbpl.mozilla.org/php/getParsedLog.php?id=30445739&tree=Mozilla-Inbound
https://tbpl.mozilla.org/php/getParsedLog.php?id=30445414&tree=Mozilla-Inbound
https://tbpl.mozilla.org/php/getParsedLog.php?id=30446297&tree=Mozilla-Inbound
https://tbpl.mozilla.org/php/getParsedLog.php?id=30446502&tree=Mozilla-Inbound
Shu and RyanVM both suspect that https://hg.mozilla.org/integration/mozilla-inbound/rev/ce4011f33422 was the cause for the failures, but I backed out the whole push just to be sure.
https://hg.mozilla.org/mozilla-central/rev/d9ad4cc32e5d
https://hg.mozilla.org/mozilla-central/rev/011dcedf181f
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla28
Comment 9•12 years ago
|
||
backout completed as part of https://tbpl.mozilla.org/?tree=Mozilla-Inbound&rev=494827a9190e as part of discussion in https://bugzilla.mozilla.org/show_bug.cgi?id=937997#c48
remote: https://hg.mozilla.org/integration/mozilla-inbound/rev/b0e18dd50141
remote: https://hg.mozilla.org/integration/mozilla-inbound/rev/0bfc071cd47c
remote: https://hg.mozilla.org/integration/mozilla-inbound/rev/4e3a84277bd2
remote: https://hg.mozilla.org/integration/mozilla-inbound/rev/01b9888de10c
remote: https://hg.mozilla.org/integration/mozilla-inbound/rev/5c1d58a7dfc9
remote: https://hg.mozilla.org/integration/mozilla-inbound/rev/3382fad9edf0
remote: https://hg.mozilla.org/integration/mozilla-inbound/rev/49229e7d1afd
remote: https://hg.mozilla.org/integration/mozilla-inbound/rev/494827a9190e
however see bug 937997 for investigations going on for the root cause and tree reopening
Assignee | ||
Updated•12 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 10•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/dd7de34a6f34
https://hg.mozilla.org/mozilla-central/rev/e1e55ac4e33d
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Assignee | ||
Comment 11•12 years ago
|
||
Assignee | ||
Comment 12•12 years ago
|
||
Assignee | ||
Comment 13•12 years ago
|
||
Comment on attachment 8341333 [details] [diff] [review]
Part 1: Add Debugger.Script.lineCount test where the script's source notes end in newline notes. (
[Approval Request Comment]
Bug caused by (feature/regressing bug #):
Bug 754201 most recently. Not sure what introduced AutoDebugModeGC initially.
User impact if declined:
Firebug unusable with many tabs. Firebug has worked around this by disabling JITs permanently if it's on, which is in some ways worse since it slows down *all* tabs.
Testing completed (on m-c, etc.):
On m-c.
Risk to taking this patch (and alternatives if risky):
GC behavior changes surfacing existing leaks/OOMs. When landing on m-c new leaks were surfaced (and eventually fixed). I am nominating those fixes for uplift also.
String or IDL/UUID changes made by this patch:
None
The Firebug slowness metabug is bug 815603. List of bugs I'm nominating for uplift in this batch:
- bug 936143
- bug 935228
- bug 933882
- bug 935470
- bug 942346
- bug 934799
Attachment #8341333 -
Flags: approval-mozilla-beta?
Attachment #8341333 -
Flags: approval-mozilla-aurora?
Assignee | ||
Comment 14•12 years ago
|
||
Comment on attachment 8341335 [details] [diff] [review]
Part 2: Simplify and fix js_GetScriptLineExtent. (
[Approval Request Comment]
Bug caused by (feature/regressing bug #):
Bug 754201 most recently. Not sure what introduced AutoDebugModeGC initially.
User impact if declined:
Firebug unusable with many tabs. Firebug has worked around this by disabling JITs permanently if it's on, which is in some ways worse since it slows down *all* tabs.
Testing completed (on m-c, etc.):
On m-c.
Risk to taking this patch (and alternatives if risky):
GC behavior changes surfacing existing leaks/OOMs. When landing on m-c new leaks were surfaced (and eventually fixed). I am nominating those fixes for uplift also.
String or IDL/UUID changes made by this patch:
None
The Firebug slowness metabug is bug 815603. List of bugs I'm nominating for uplift in this batch:
- bug 936143
- bug 935228
- bug 933882
- bug 935470
- bug 942346
- bug 934799
Attachment #8341335 -
Flags: approval-mozilla-beta?
Attachment #8341335 -
Flags: approval-mozilla-aurora?
Updated•12 years ago
|
Comment 15•12 years ago
|
||
Comment on attachment 8341333 [details] [diff] [review]
Part 1: Add Debugger.Script.lineCount test where the script's source notes end in newline notes. (
We can take this on Aurora and thus it will be on Beta in a week, but we're way past the point of taking untracked, major change to Firefox 26 as we are going to build our final candidate today as well as the RC.
Attachment #8341333 -
Flags: approval-mozilla-beta?
Attachment #8341333 -
Flags: approval-mozilla-beta-
Attachment #8341333 -
Flags: approval-mozilla-aurora?
Attachment #8341333 -
Flags: approval-mozilla-aurora+
Updated•12 years ago
|
Attachment #8341335 -
Flags: approval-mozilla-beta?
Attachment #8341335 -
Flags: approval-mozilla-beta-
Attachment #8341335 -
Flags: approval-mozilla-aurora?
Attachment #8341335 -
Flags: approval-mozilla-aurora+
Assignee | ||
Comment 16•12 years ago
|
||
Updated•12 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•