3 ms·

Great to hear that Firefox on macOS might get snappier with these changes. The reliance on undocumented APIs is the only potential red flag. Out of curiosity,

by jhatax 4y ago

Great to hear that Firefox on macOS might get snappier with these changes. The reliance on undocumented APIs is the only potential red flag. Out of curiosity, does Chromium use spinlocks on macOS? If they do in a scenario where characteristics need to be similar to the jemalloc use case, how are they accomplishing the outcome?

l1n 4y ago
looks like they just use system malloc: https://chromium.googlesource.com/chromium/src/base/+/master/allocator/README.md https://chromium.googlesource.com/chromium/src/base/+/master...
- garaetjjte 4y ago
  This document is outdated, PartitionAlloc is used for all allocations now: https://chromium.googlesource.com/chromium/src/+/ec6b52f91a4cfa3fe28fd7cf2c3662efb1d55235 https://chromium.googlesource.com/chromium/src/+/ec6b52f91a4... It uses plain os_unfair_lock: https://chromium.googlesource.com/chromium/src.git/+/refs/heads/main/base/allocator/partition_allocator/spinning_mutex.h#51 https://chromium.googlesource.com/chromium/src.git/+/refs/he... EDIT: It also combines os_unfair_lock with manual PAUSE spinning.