| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
| |
This should be the last code backout for this. merging this branch
should get us back to the way we were (+ additional code changes for
later changes) as fasr as the unused unboxed code is concerned.
|
|
|
|
|
| |
- accounting for removal of watch()/unwatch()
- updated for intermediate code changes.
|
|
|
|
| |
Tag #1287
|
|
|
|
| |
This resolves #1302.
|
|
|
|
| |
Resolves #1284.
|
| |
|
| |
|
| |
|
|
|
|
| |
JSErrorReport.{notes,freeNotes}.
|
| |
|
| |
|
|
|
|
|
| |
This should be all that's needed for #1017, but verification of
impact is definitely desired.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch fixes two related issues.
1. The AutoStopwatch uses a stack-allocated `mozilla::Vector` to
communicate with its callback during each compartment switch.
This vector was designed to allow its contents to be stack-allocated
but they turned out to be accidentally heap-allocated.
2. During each tick, the stopwatch fills a vector `recentGroups_`.
This vector always started with minimal capacity and had to grow
repeatedly as groups were added, causing repeated reallocations.
This patch preallocates `recentGroups_` to have the same capacity as the
previous tick. We expect that this should eventually reach a stable size
that closely matches the actual needs of the process.
|
|
|
|
| |
This reverts commit 3476c1d60ec29c5497123194acd7a9310b1023d2.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch fixes two related issues.
1. The AutoStopwatch uses a stack-allocated `mozilla::Vector` to
communicate with its callback during each compartment switch.
This vector was designed to allow its contents to be stack-allocated
but they turned out to be accidentally heap-allocated.
2. During each tick, the stopwatch fills a vector `recentGroups_`.
This vector always started with minimal capacity and had to grow
repeatedly as groups were added, causing repeated reallocations.
This patch preallocates `recentGroups_` to have the same capacity as the
previous tick. We expect that this should eventually reach a stable size
that closely matches the actual needs of the process.
|
| |
|
|
|
|
| |
Standards Compliance fix, port of Bug 1492737
|
| |
|
|\
| |
| |
| | |
js_array_values_1
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bug 1342553 - Part 0.1: Use try-catch for IteratorClose in for-of
Bug 1343072 - Update HasLiveStackValueAtDepth to follow the change in
JSTRY_FOR_OF
Bug 1344753 - Update for-of stack depth in
ControlFlowGenerator::processWhileOrForInLoop
Issue #74
|
| |
| |
| |
| |
| |
| | |
Issue #78
[Depends on] Bug 883377: Implement ES6 function "name" property
semantics
|
| | |
|
| |
| |
| |
| | |
Issue #17
|
|/ |
|
|\ |
|
| | |
|
|/ |
|
|
|
|
| |
UXP repo issue #8
|
|
|
|
|
| |
Pref: javascript.options.mem.gc_generational
This resolves #20
|
|
|