This moves it to the same compartment as the code that it interfaces with the
most often, and allows for much more effective JIT optimizations.
MozReview-Commit-ID: FZcogI4d4rv
The test was failing on 56 beta because the new console frontend isn't enabled there and thus
the ObjectInspector that were tested not in the old frontend.
This patch adds a branch in the test so we can wait for the correct element (VariableView or ObjectInspector)
depending on whether the new console frontend is enabled or not.
MozReview-Commit-ID: HGGgr7CWMpe
The test was failing on 56 beta because the new console frontend isn't enabled there and thus
the ObjectInspector that were tested not in the old frontend.
This patch adds a branch in the test so we can wait for the correct element (VariableView or ObjectInspector)
depending on whether the new console frontend is enabled or not.
MozReview-Commit-ID: HGGgr7CWMpe
Pulls out the CppFiltParser work into a worker to run in the
background and avoid the jank induced by the final
convertSymsMapToExpectedSymFormat call.
Profiling shows that after this change there is virtually no
jank when asking the geckoProfiler API for symbols.
MozReview-Commit-ID: CAKMvjLa4dl
Pulls out the NMParser work (parsing nm results and turning
them into an ArrayBuffer'd map of addresses to symbols) into
a worker.
For OSX we will still need to do some work to run c++filt in the
background, but this gets us most of the way there. Without a
Subprocess.jsm usable from a worker, we'll have to bounce data
back to the main thread in order to bounce it to the c++filt
worker.
MozReview-Commit-ID: LZi7J1qGpmh
* Toggle animate=false attribute on arrow panels when toolkit.cosmeticAnimations.enabled is false
* Use preferences-service component to lookup the pref in the arrowpanel binding
* Disable this pref during tests to remove a source of instability and timing-based test failures in chrome/UI tests.
* Enable cosmeticAnimations for tests which depend on existing behavior
* Re-enable cosmeticAnimations pref for browser_ext_popup_select.js which is known to be more reliable with animations
MozReview-Commit-ID: IvA2ySPPmeJ
* Toggle animate=false attribute on arrow panels when toolkit.cosmeticAnimations.enabled is false
* Use preferences-service component to lookup the pref in the arrowpanel binding
* Disable this pref during tests to remove a source of instability and timing-based test failures in chrome/UI tests.
* Enable cosmeticAnimations for tests which depend on existing behavior
* Re-enable cosmeticAnimations pref for browser_ext_popup_select.js which is known to be more reliable with animations
MozReview-Commit-ID: IvA2ySPPmeJ
The inspect command in extension was directly calling jsterm.inspectObject and doing so bypassed
the code we implemented for the command on the new frontend (i.e. no more variable view).
This patch modifies the jsterm inspectObject function so it can do the expected behavior,
and also reverts some changes made in the original inspect command bug, so we only deal with
the new frontend code in jsterm.inspectObject.
This implied changing an extension test that was waiting for the variable view to boot-up.
The test was modified to match the tests we already have for the inspect command on the new
console frontend.
MozReview-Commit-ID: 8fZV20Mck8r
