System memory allocator free operation zeroes out deallocated blocks in iOS 16

• glibc

  45 1,213 9.8 C

  Unofficial mirror of sourceware glibc repository. Updated daily. (by bminor)

  

That depends on the specific implementation. glibc does unmap memory[1]. Not in every free() call, but still. There are also implementations which unmap in every free(), which are used to quickly detect bugs. Honestly, I wouldn't want to use an implementation which never unmaps memory. I've already been irritated by Go's reluctance to return memory to the OS in the past. I'm certainly glad it's less of a problem in C. (Although I've read some reports of glibc being a bit suboptimal here in multithreaded programs, compared to allocators like tcmalloc or jemalloc.)

[1]: <https://github.com/bminor/glibc/blob/a364a3a7090b82ddd30e920...>

• dlmalloc

  1 221 10.0 C

  Doug Lea's memory allocator

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• jemalloc

  34 9,060 8.3 C
  

• tcmalloc

  15 4,081 9.8 C++
  

Suggest a related project