code wiki / _hdl_build / nx_gcscope_test.nx

nx_gcscope_test.nx

buildroot/runtime/_hdl_build/nx_gcscope_test.nx

1748 B25 linesdepth 7pulls 22 transitivereach 0 importersview sourcekind gate/proof
docsdependenciesstructsconstsfunctions

about

nx_gcscope_test.nx -- SYSTEMATIC hypothesis for the context-dependent jQuery failures: does GC collect a CLOSURE-CAPTURED var under heavy allocation? Sizzle captures `document` in its IIFE scope then allocates massively (matchers, caches) -> if GC doesn't mark closure-captured envs, the var reads undefined at scale.

dependencies 2 imports · 0 importers

nx_syscalls.nx nx_js_eval.nx nx_gcscope_test.nx

imports: nx_syscalls.nxnx_js_eval.nx

imported by: nobody (leaf or entry point)

call flow from main pre-order; caps 40 nodes / depth 6 declared; ↻ = already shown

main run1 js_set_rt_dbg sys_mmap slen cw sys_write slen ↻ js_pending_total js_pending_url ev_str_bytes str_flatten ev_str_new nx_pool_alloc nx_pool_alloc ↻ ev_str_len

structs

none

consts

none

functions

6func slen(s: *u8) -> i64 { var n: i64=0; while s[n]!=(0 as u8){n=n+1} return n }
called by 2: cwrun1
7func cw(s: *u8) -> i64 { sys_write(1,s,slen(s)); return 0 }
called by 1: run1 calls 2: sys_writeslen
8func run1(label: *u8, js: *u8) -> i64
19func main() -> i64
calls 1: run1