msgspec-struct-gc-check

To safely use gc=False on a msgspec.Struct, you must verify the object graph is cycle-free, container fields do not mutate to create back-references, and type definitions are __slots__ compatible.

You should not disable garbage collection on a Python struct if its fields include nested containers that mutate, or if the object graph risks creating reference cycles that standard garbage collection would normally clean up.

Static analysis detects reference cycles by reviewing field types, nested structs, and container relationships within the msgspec.Struct definition to identify leak-prone back-references before recommending gc=False.

Yes, you can use gc=False with msgspec.Struct types containing generic mixins, provided the audit confirms the mixins maintain a cycle-free object graph and do not introduce mutating container behavior.

The best way to audit for hidden memory leaks is to perform a mutation audit on list, dict, or set fields to ensure they are never mutated in ways that could create back-references, alongside cycle safety checks.

msgspec.Struct gc=False works with nested containers only if a static analysis audit verifies the container behavior is non-mutating and the nested relationships remain strictly cycle-free.