Ian Bull

> That's because we need to pass a proper CLI flag to V8 to make this API available. All the other unstable APIs are our own APIs that we can...

> Sorry, I just assumed JSONC was handled [in JavaScript](https://deno.land/std/jsonc/mod.ts) and not in Rust. There is also a Rust implementation here: https://github.com/denoland/deno_config. There are a lot of goodies around Deno...

I did a bit of analysis with this project loaded. Here's what I did and some findings: - I loaded the project linked to the description above - I used...

I wonder if we've tried to use `--max-old-space-size=` with the embedded V8. One theory is that V8 doesn't really _need_ that much memory, but it will happily use it. Once...

I've spent some more time on this. I created a patched LSP that invokes the V8 Garbage Collector after each `tsc` request. On a Mac M1, on a fairly small...

I've also added some V8 Heap Statistics to my patched LSP. In particular, I've been monitoring: ``` heap_stats.malloced_memory(), heap_stats.external_memory(), heap_stats.used_heap_size(), ``` These seem to stay fairly stable, and show nothing...

I went in a slightly different direction today and focused back on the Linter. The following snippet shows unbounded memory growth: ```rust use deno_ast::parse_module; use deno_ast::MediaType; use deno_ast::ParseParams; use deno_ast::SourceTextInfo;...

There was in fact a leak in dprint-swc-ext which @dsherret addressed today [1]. This should land in 1.41.0. I've done some testing with this change-set applied and things seem much...

``` Deno 1.25.3 exit using ctrl+d or close() > Deno.build { target: "aarch64-apple-darwin", arch: "aarch64", os: "darwin", vendor: "apple", env: undefined } ```

Ah, looks like it's related to the Mac M1 (arm) architecture.