зеркало из https://github.com/mozilla/gecko-dev.git
d17a9a9a55
Now that `fix_stacks.py` is being used instead of `fix_macosx_stack.py`, stack-fixing time has dropped from about 14 minutes to about 30 seconds on my new MacBook Pro. Also, print a warning about stacks not being fixed if `MOZ_DISABLE_STACK_FIX` is set. This warning shows up at the start of the test run. Also, print a warning about stack fixing slowness, because 30 seconds is long enough to possibly be surprising. This warning shows up just before the first stack frame is fixed, like this: ``` Assertion failure: false (BEEP BOOP), at /home/njn/moz/au3/dom/base/nsGlobalWindowOuter.cpp:1342 Initializing stack-fixing for the first stack frame, this may take a while... #01: nsGlobalWindowOuter::nsGlobalWindowOuter(unsigned long) (/home/njn/moz/au3/dom/base/nsGlobalWindowOuter.cpp:1342) #02: ... ``` Differential Revision: https://phabricator.services.mozilla.com/D65676 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| bloatview | ||
| browsertime | ||
| clang-tidy | ||
| code-coverage | ||
| compare-locales | ||
| coverity | ||
| crashreporter | ||
| fuzzing | ||
| github-sync | ||
| infer | ||
| jprof | ||
| leak-gauge | ||
| lint | ||
| moztreedocs | ||
| performance | ||
| phabricator | ||
| power | ||
| profiler | ||
| quitter | ||
| rb | ||
| rewriting | ||
| sanitizer/docs | ||
| tryselect | ||
| update-packaging | ||
| update-verify | ||
| vcs | ||
| mach_commands.py | ||
| moz.build | ||