[M147] Fix RangeError during AST parsing in SourceMapScopesInfo Original change's description: > Fix RangeError during AST parsing in SourceMapScopesInfo > > The recursive methods in SourceMapScopesInfo for creating AST and > searching scope and range chains caused RangeError: Maximum Call Stack > Size Exceeded on highly nested scripts. > > This refactors them into iterative methods using explicit stacks and > while loops. > > Fixed: 495542144 > Change-Id: I384e4d1e5eaf8faa4485558b7868c6e8600c4fb5 > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/7693621 > Reviewed-by: Philip Pfaffe <pfaffe@chromium.org> > Auto-Submit: Simon Zünd <szuend@chromium.org> > Commit-Queue: Philip Pfaffe <pfaffe@chromium.org> (cherry picked from commit 5717d940b6563e8f5926cd8428423e7d588e3200) Bug: 496840714,495542144 Change-Id: I384e4d1e5eaf8faa4485558b7868c6e8600c4fb5 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/7704582 Auto-Submit: Chrome Cherry Picker <chrome-cherry-picker@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com. Check out the Chromium DevTools documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.
DevTools frontend repository is mirrored on GitHub.
DevTools frontend is also available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may require some effort.
The version number of the npm package (e.g. 1.0.373466) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.
There are a few options to keep an eye on the latest and greatest of DevTools development:
Follow What's new in DevTools.
Follow Umar's Dev Tips.
Follow these individual Twitter accounts: @umaar, @malyw, @kdzwinel, @addyosmani, @paul_irish, @samccone, @mathias, @mattzeunert, @PrashantPalikhe, @ziyunfei, and @bmeurer.
Follow to g/devtools-reviews@chromium.org mailing list for all reviews of pending code, and view the log, or follow @DevToolsCommits on Twitter.
Checkout all open DevTools tickets on crbug.com
Use Chrome Canary and poke around the experiments.