[nautilus] application: Remove custom allocation default size
- From: Carlos Soriano <csoriano src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [nautilus] application: Remove custom allocation default size
- Date: Mon, 12 Feb 2018 14:30:56 +0000 (UTC)
commit 1e5c92f8cfb543228896d03f996818f7beb2a6f8
Author: Carlos Soriano <csoriano gnome org>
Date: Mon Feb 12 15:27:55 2018 +0100
application: Remove custom allocation default size
We no longer have the desktop around, so seems this is not necessary
anymore (I'm pretty sure this wouldn't be necessary nowadays either
way...).
src/nautilus-main.c | 14 --------------
1 file changed, 14 deletions(-)
---
diff --git a/src/nautilus-main.c b/src/nautilus-main.c
index c1fff44de..456aed2d6 100644
--- a/src/nautilus-main.c
+++ b/src/nautilus-main.c
@@ -56,20 +56,6 @@ main (int argc,
gint retval;
NautilusApplication *application;
-#if defined (HAVE_MALLOPT) && defined(M_MMAP_THRESHOLD)
- /* Nautilus uses lots and lots of small and medium size allocations,
- * and then a few large ones for the desktop background. By default
- * glibc uses a dynamic treshold for how large allocations should
- * be mmaped. Unfortunately this triggers quickly for nautilus when
- * it does the desktop background allocations, raising the limit
- * such that a lot of temporary large allocations end up on the
- * heap and are thus not returned to the OS. To fix this we set
- * a hardcoded limit. I don't know what a good value is, but 128K
- * was the old glibc static limit, lets use that.
- */
- mallopt (M_MMAP_THRESHOLD, 128 * 1024);
-#endif
-
if (g_getenv ("NAUTILUS_DEBUG") != NULL)
{
eel_make_warnings_and_criticals_stop_in_debugger ();
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]