Hello, In a large heap program I am working on, I noticed a peculiar change in the way virtual memory is reserved by the runtime : with comparable heap size (about 150GB) and virtual memory size (growing to 400-500GB probably due to a kind of fragmentation), the number of distinct memory mappings has apparently increased between Go 1.11 and Go 1.12 reaching the system limit (Linux setting vm.max_map_count).
Is it something that has been experienced by someone else ? I don't believe this classifies as a bug, but I was a bit surprised (especially as I wasn't aware of that system limit). Rémy -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
