| commit | 4b26ea0dad260fb6500b83a8960950d4cc6e5e04 | [log] [tgz] |
|---|---|---|
| author | Jens Johansen <jensj@google.com> | Thu Jan 27 09:55:51 2022 +0000 |
| committer | Commit Bot <commit-bot@chromium.org> | Thu Jan 27 09:55:51 2022 +0000 |
| tree | 373c00ad9d74d021b94040881607862be89b6c88 | |
| parent | 13713c2232fb9a8bc1457d01184c2527d1a04f99 [diff] |
[CFE] Fix incremental_compiler_leak_test(er) In https://dart-review.googlesource.com/c/sdk/+/214020 incremental_compiler_leak_test was renamed to incremental_compiler_leak_tester temporarily because it started saying we had possible leaks. Looking into it now, a number of puzzeling this were found: * Many SourceLibraryBuilders, SourceClassBuilders etc was alive despite having been converted to DillLibraryBuilders (etc). They shoudn't be. * Several Librarys (from kernels AST) came and went between invalidations. This all was caused by the VM sometimes keeping things around longer than it should (probably a variation of https://github.com/dart-lang/sdk/issues/36983). This CL fixes it by explicitley nulling things out (and similar). It re-enasbles the test and updates it to explicitley expecting a certain number of instances for some classes (e.g. it now expect 0 SourceLibraryBuilders). To be clear I don't think this has caused any "real" leaks, but: * having things clear up too late is very confusing. * we will probably use less memory now. Change-Id: I3a439f23fc7ef26b156c6164a2c37f6352bc57b4 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/229964 Reviewed-by: Johnni Winther <johnniwinther@google.com> Commit-Queue: Jens Johansen <jensj@google.com>
Dart is:
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents on our wiki.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.