summaryrefslogtreecommitdiff
path: root/storage
diff options
context:
space:
mode:
authorwolfbeast <mcwerewolf@wolfbeast.com>2020-01-23 15:17:51 +0100
committerwolfbeast <mcwerewolf@wolfbeast.com>2020-01-23 15:17:51 +0100
commita64ac6d7022e4c88149d897864f857dce1063249 (patch)
tree0abaa12cb30d5ee92e56bef895b8e58b4b35aff8 /storage
parent6d761aa68fd6d3ae91ad4fb34c80c85d7e665c79 (diff)
downloaduxp-a64ac6d7022e4c88149d897864f857dce1063249.tar.gz
No issue - Always use jemalloc allocator for storage memory when
MOZ_MEMORY is defined (which is defined by enabling jemalloc in config)
Diffstat (limited to 'storage')
-rw-r--r--storage/moz.build9
1 files changed, 1 insertions, 8 deletions
diff --git a/storage/moz.build b/storage/moz.build
index 216a1cf742..5ccfabd715 100644
--- a/storage/moz.build
+++ b/storage/moz.build
@@ -88,17 +88,10 @@ FINAL_LIBRARY = 'xul'
# Don't use the jemalloc allocator on Android, because we can't guarantee
# that Gecko will configure sqlite before it is first used (bug 730495).
#
-# Don't use the jemalloc allocator when using system sqlite. Linked in libraries
-# (such as NSS) might trigger an initialization of sqlite and allocation
-# of memory using the default allocator, prior to the storage service
-# registering its allocator, causing memory management failures (bug 938730).
-# However, this is not an issue if both the jemalloc allocator and the default
-# allocator are the same thing.
-#
# Note: On Windows our sqlite build assumes we use jemalloc. If you disable
# MOZ_STORAGE_MEMORY on Windows, you will also need to change the "ifdef
# MOZ_MEMORY" options in db/sqlite3/src/Makefile.in.
-if CONFIG['MOZ_MEMORY'] and not CONFIG['MOZ_SYSTEM_SQLITE']:
+if CONFIG['MOZ_MEMORY']:
if CONFIG['OS_TARGET'] != 'Android':
DEFINES['MOZ_STORAGE_MEMORY'] = True