summaryrefslogtreecommitdiffstats
path: root/memory
Commit message (Collapse)AuthorAgeLines
* Issue #187: Remove solaris 1st party code OS checks.wolfbeast2019-03-30-5/+0
|
* Issue #187: Remove solaris conditional code.wolfbeast2019-03-30-25/+2
|
* Silence the -Wuninitialized warning in mozjemalloctrav902018-09-08-1/+4
| | | | GCC 7+ warns about too many false positives.
* Revert "Switch to using a single memory allocation arena"wolfbeast2018-09-01-1/+1
| | | | This reverts commit 4ceb21241eacac2911f2fed846359215870f121f.
* Switch to using a single memory allocation arenawolfbeast2018-08-25-1/+1
|
* Remove the Dark Matter Detector (DMD) Memeory debugger component.wolfbeast2018-05-23-6153/+0
| | | | This resolves #376.
* Remove MOZ_WIDGET_GONK [2/2]wolfbeast2018-05-13-14/+2
| | | | Tag #288
* Use slim reader/writer locks instead of critical sections.wolfbeast2018-04-28-13/+8
|
* Remove the unused and rudimentary arena load balancer.wolfbeast2018-04-28-252/+4
| | | | | 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.wolfbeast2018-04-28-21/+19
|
* Remove single-threaded considerations.wolfbeast2018-04-27-52/+30
| | | | We assume our applications are always going to have multithreaded access to the malloc.
* Update credits in BSD-licensed files.wolfbeast2018-04-27-7/+7
|
* Remove jemalloc 4 leftover conditional.wolfbeast2018-04-27-2/+0
|
* Remove MOZ_REPLACE_JEMALLOCwolfbeast2018-04-27-6/+2
| | | | This was only defined when building jemalloc4 as a replace-malloc library.
* Remove jemalloc 4 from our tree.wolfbeast2018-04-27-73367/+4
|
* Remove support for making jemalloc4 the default memory allocator.wolfbeast2018-04-27-361/+15
|
* Remove support for system jemalloc.wolfbeast2018-04-26-48/+29
|
* Bug 1424709 - Force disable the OSX system "nano allocator". r=spohl, a=RyanVMMike Hommey2018-03-14-0/+6
| | | | | | | | | | | 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.htrav902018-03-04-0/+6
| | | | 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.0Matt A. Tobin2018-02-02-0/+94028