Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Issue mcp-graveyard/UXP%187: Remove solaris 1st party code OS checks. | wolfbeast | 2019-03-30 |
| | |||
* | Issue mcp-graveyard/UXP%187: Remove solaris conditional code. | wolfbeast | 2019-03-30 |
| | |||
* | Silence the -Wuninitialized warning in mozjemalloc | trav90 | 2018-09-08 |
| | | | | GCC 7+ warns about too many false positives. | ||
* | Revert "Switch to using a single memory allocation arena" | wolfbeast | 2018-09-01 |
| | | | | This reverts commit 4ceb21241eacac2911f2fed846359215870f121f. | ||
* | Switch to using a single memory allocation arena | wolfbeast | 2018-08-25 |
| | |||
* | Remove the Dark Matter Detector (DMD) Memeory debugger component. | wolfbeast | 2018-05-23 |
| | | | | This resolves %376. | ||
* | Remove MOZ_WIDGET_GONK [2/2] | wolfbeast | 2018-05-13 |
| | | | | Tag mcp-graveyard/UXP%288 | ||
* | Use slim reader/writer locks instead of critical sections. | wolfbeast | 2018-04-28 |
| | |||
* | Remove the unused and rudimentary arena load balancer. | wolfbeast | 2018-04-28 |
| | | | | | Lock contention is not something we'd easily have to deal with in our application. This simplifies our code. | ||
* | Make our allocator use multiple arenas based on number of CPU cores. | wolfbeast | 2018-04-28 |
| | |||
* | Remove single-threaded considerations. | wolfbeast | 2018-04-27 |
| | | | | We assume our applications are always going to have multithreaded access to the malloc. | ||
* | Update credits in BSD-licensed files. | wolfbeast | 2018-04-27 |
| | |||
* | Remove jemalloc 4 leftover conditional. | wolfbeast | 2018-04-27 |
| | |||
* | Remove MOZ_REPLACE_JEMALLOC | wolfbeast | 2018-04-27 |
| | | | | This was only defined when building jemalloc4 as a replace-malloc library. | ||
* | Remove jemalloc 4 from our tree. | wolfbeast | 2018-04-27 |
| | |||
* | Remove support for making jemalloc4 the default memory allocator. | wolfbeast | 2018-04-27 |
| | |||
* | Remove support for system jemalloc. | wolfbeast | 2018-04-26 |
| | |||
* | Bug 1424709 - Force disable the OSX system "nano allocator". r=spohl, a=RyanVM | Mike Hommey | 2018-03-14 |
| | | | | | | | | | | | 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 | ||
* | Use |noexcept| instead of an exception-specification in mozalloc.h | trav90 | 2018-03-04 |
| | | | | 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. | ||
* | Add m-esr52 at 52.6.0 | Matt A. Tobin | 2018-02-02 |