| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
| |
Lock contention is not something we'd easily have to deal with in our application.
This simplifies our code.
|
| |
|
|
|
|
| |
We assume our applications are always going to have multithreaded access to the malloc.
|
| |
|
| |
|
|
|
|
| |
This was only defined when building jemalloc4 as a replace-malloc library.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
We're not actually using it, and it messes up with the zone allocator in
mozjemalloc after fork(). See the lengthy analysis in
https://bugzilla.mozilla.org/show_bug.cgi?id=1424709#c34 and following.
--HG--
extra : rebase_source : b191048290a907cc7668ad7ab6369ef8661f31dc
extra : intermediate-source : 45c5d467a46077dcc3ccd59feafd0c2784432fef
extra : source : bf1efa161edb20a83fe8db2f96c51f4e66880153
|
|
|
|
| |
We are using |throw(std::bad_alloc)|, but dynamic exception specifications have been deprecated in C++11. The C++11 equivalent is |noexcept(false)|. This causes build warning spam when using newer compilers such as GCC 7.x.
|
|
|