xaurx

signed

it is still an issue if one tries to run inside k8s container with read only root file system. if nobody objects I would simply ignore ```read-only file system``` and...

It's possible to show code privately under NDA. Works for you?

Let me check. Maybe I can collect/provide some info which would be helpful?

ok. Can we send them to email in your github profile?

@cespare yes, it's a fresh worker using the same code cache, i.e. not downloading it again. To reproduce locally I used `go clean -cache` between the runs: w/o generics: ```...

@mdempsky see exact commands I used to reproduce in above message. i.e. it's not about some other changes in the code. any fresh build after `go clean -cache` takes 4.2x...

@punya will check with NoAllocProfiling=true. @aalexand unfortunately GCP profiler doesn't show "count" metric (or I have not found it). All it says that top profiles are about ~18GB, i.e. assuming...

@punya disabling AllocProfiling helped, confirm. @aalexand "count" metric is about ~40M in top profiles. My guess is that the ones which caused OOM were having even more events.

@punya these are bad defaults if everybody has to disable it.