зеркало из https://github.com/mozilla/gecko-dev.git
2a318e8c71
1. The current asynchronous behavior is pointless, because we still remove the hashtable entry synchronously, which deletes the value, and it's the value we're using. 2. Trying to asynchronously delete the value is difficult, and not currently needed because we can't get a memory-pressure notification while we're using the value, and hence can't expire it from the expiration tracker. Note: we can't get this memory-pressure notification because the stage 2 of mozalloc_handle_oom() to reclaim memory when OOM is not implemented yet. |
||
|---|---|---|
| .. | ||
| build | ||
| fallible | ||
| gtest | ||
| jemalloc | ||
| mozalloc | ||
| mozjemalloc | ||
| replace | ||
| volatile | ||
| moz.build | ||