On Tuesday 2016-05-31 12:50 -0400, Benjamin Smedberg wrote: > It's likely that this particular report is running out of VM, yes. jemalloc > allocates new memory chunks in large blocks (1MB?), and with only 122MB of > VM it's likely that a lot of that is inaccessible, either because of > fragmentation or because sites are allocating VM blocks of less than 64k, > which is the allocation resolution of Windows VM. > > If you look at the raw dump tab, you'll see: > > "largest_free_vm_block": "0xf0000" - which is 983040 bytes, less than 1MB.
Would it make sense for jemalloc to try allocating memory in smaller chunks when large ones aren't available? -David -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla https://www.mozilla.org/ 𝄂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914)
signature.asc
Description: PGP signature
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
