fix: identified and fixed a memory leak from JsRuntime

I had to use the cargo patch to fix the memory leakage problem because the root cause of the memory leak belonged to `deno_core`. Eventually, these changes should be tracked at `deno_core`; so until fixing this problem upstream, we have to use the patch. It could be the substantial solution for #212 and #192 (on the assumption that I found all memory leakage places of `JsRuntime` 😋 For reference, Valgrind no longer reported definite memory leakage after this patch) (cherry picked from commit bc631b4)
supabase · Jan 20, 2024 · 93ee272 · 93ee272
1 parent b9268ad
commit 93ee272
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 7 deletions.
diff --git a/.cargo/config.toml b/.cargo/config.toml
@@ -0,0 +1,2 @@
+[env]
+RUSTY_V8_MIRROR = "https://github.com/nyannyacha/rusty_v8/releases/download"
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/Cargo.toml b/Cargo.toml
@@ -69,6 +69,7 @@ futures-util = { version = "0.3.28" }
 
 [patch.crates-io]
 deno_core = { git = "https://github.com/nyannyacha/deno_core", branch = "222" }
+v8 = { git = "https://github.com/nyannyacha/rusty_v8", branch = "rokat" }
 
 [profile.release]
 lto = true