Tracking Deno memory leaks

This repository contains a minimal example that shows whether a particular Deno runtime version has memory leaks or not.

No leaks are especially desirable in an environment where the same server process handles many FaaS calls.

Steps to reproduce:

Build, sign, and run the binary with the following command:

cargo build && codesign-for-instruments target/debug/deno-memleak && target/debug/deno-memleak

Open Instruments.app on macOS, select the "Leaks" template, attach it to the running deno-memleak process, and start recording (Cmd+R).

The result will look like this if there are any leaks:

Fixed leaks:

• Memory leak when transpiling modules during bootstrap Fixed in Deno 1.45.0
• CFunctionInfo/CTypeInfo leak in OpCtx: denoland/deno_core#714 / denoland/deno#24169 Fixed in Deno 1.46.0

Known open leaks:

none 💪