13
edits
Mozilla 2/Memory/OOM API: Difference between revisions
m
→Memory reserve API
(Add thread safety note, add temporary notification disabling.) |
|||
| Line 75: | Line 75: | ||
* Callback functions can freely call back into the allocator (i.e. the | * Callback functions can freely call back into the allocator (i.e. the | ||
* allocator releases all internal resources before calling each callback | * allocator releases all internal resources before calling each callback | ||
* function), though | * function), though allocation is discouraged, since recursive callbacks are | ||
* | * likely to result, which places extra burden on the application to avoid | ||
* | * deadlocking. | ||
* | * | ||
* Callback functions must be thread-safe, since it is possible that multiple | * Callback functions must be thread-safe, since it is possible that multiple | ||