codegraph 1.3.1 init takes 23min and still processing

[sniperrenren]

MACBOOK Apple M1
OS Version macOS Tahoe 26.5.2 (25F84)

please make it right

[colbymchenry]

Thanks for the detailed screenshot — the version comparison and the CODEGRAPH_NO_WATCHDOG=1 run made this quick to pin down.

Root cause: one of the dynamic-dispatch analysis passes that runs at the end of "Resolving refs" only ever applies to Swift/Kotlin code, but it was scanning every function in every language. On a PHP/JS codebase like yours it can never produce anything, yet .push(/.add(-heavy JavaScript triggers its scanning constantly — and its per-match bookkeeping was quadratic on large functions (and about twice as slow again on non-ASCII text, e.g. Chinese comments/strings). That's the 20+ minute grind stuck at 97%, and a single big generated function inside it could block long enough that the safety watchdog killed the run. Your project indexed fine on 0.9.9 because 1.x extracts a lot more symbols from the same files, which pushed this latent cost over the cliff.

Fixed in #1237 (merged): the pass now skips languages it can't apply to and its bookkeeping is no longer quadratic. On a comparable repo (CRMEB, ThinkPHP + Vue with Chinese content) the pass went from 127s to ~0 and the produced graph is byte-for-byte identical. The fix will be in the next release — after upgrading, run codegraph uninit && codegraph init (or just codegraph init) once and it should be back in the ~1 minute range like 0.9.9.

I'll leave this open until the release ships so you can confirm.