cgocheck mode can be enabled using GOEXPERIMENT (which
requires a rebuild), see https://pkg.go.dev/internal/goexperiment for details.
+ checkfinalizers: setting checkfinalizers=1 causes the garbage collector to run
+ multiple partial non-parallel stop-the-world collections to identify common issues with
+ finalizers and cleanups, like those listed at
+ https://go.dev/doc/gc-guide#Finalizers_cleanups_and_weak_pointers. If a potential issue
+ is found, the program will terminate with a description of all potential issues, the
+ associated values, and a list of those values' finalizers and cleanups, including where
+ they were created. It also adds tracking for tiny blocks to help diagnose issues with
+ those as well. The analysis performed during the partial collection is conservative.
+ Notably, it flags any path back to the original object from the cleanup function,
+ cleanup arguments, or finalizer function as a potential issue, even if that path might
+ be severed sometime later during execution (though this is not a recommended pattern).
+ This mode also produces one line of output to stderr every GC cycle with information
+ about the finalizer and cleanup queue lengths. Lines produced by this mode start with
+ "checkfinalizers:".
+
decoratemappings: controls whether the Go runtime annotates OS
anonymous memory mappings with context about their purpose. These
annotations appear in /proc/self/maps and /proc/self/smaps as