Closed catenacyber closed 1 year ago
Change https://go.dev/cl/413874 mentions this issue: debug/macho, internal/saferio: limit slice allocation
I am not sure this is resolved
When I run https://go.dev/play/p/nnJjDGt5zwW?v=gotip I still see 3Gbytes allocated
Fair point. The earlier CL saved some of the allocated memory but not all. Sent another CL.
Change https://go.dev/cl/425114 mentions this issue: debug/macho: don't use narch for seenArches map size
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Run https://go.dev/play/p/szwoyohPSJN
What did you expect to see?
The program finishing and printing somme dummy data
What did you see instead?
Only
Heap profiling shows 8Gbyte allocation including 5 from debug/macho.NewFatFile /usr/local/go/src/debug/macho/fat.go:88
Found by https://github.com/catenacyber/ngolo-fuzzing on oss-fuzz https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46182
cc @ianlancetaylor as you fixed the latest oom