Changes between Version 13 and Version 14 of WebKitGTK/TrackingMemoryErrors

Timestamp:

Oct 5, 2017, 1:28:37 AM (8 years ago)

Author:

cturner@igalia.com

Comment:

Mention that Malloc=1 is needed to succeed with Valgrind

WebKitGTK/TrackingMemoryErrors

@@ -20 +20 @@
 
 {{{
-G_SLICE=always-malloc G_DEBUG=gc-friendly,resident-modules valgrind         \
-    --tool=memcheck --leak-check=full --leak-resolution=high                \
+G_SLICE=always-malloc G_DEBUG=gc-friendly,resident-modules Malloc=1         \
+    valgrind --tool=memcheck --leak-check=full --leak-resolution=high       \
     --num-callers=20 --log-file=vgdump --smc-check=all --trace-children=yes \
     WebKitBuild/Release/bin/MiniBrowser
 }}}
 
-Here, the interesting bit is ''--trace-children=yes'', which tells valgrind to also hook into any child process spawned by the original program. For WK2 this is required if you want to check memory in the Web process (which you most likely do), otherwise it will only check it in the UI process.
+Here, the interesting bits are,
+ * ''--trace-children=yes'', which tells Valgrind to also hook into any child process spawned by the original program. For WK2 this is required if you want to check memory in the Web process (which you most likely do), otherwise it will only check it in the UI process.
+ * ''Malloc=1'', setting this environment variable will disable bmalloc, WK's custom memory allocator. bmalloc tries to allocate a large virtual memory region at startup, but this doesn't work when run under Valgrind.
 
 Notice that for both WK1 and WK2, the corresponding launcher programs are used instead of the provided script, in order to avoid checking for errors in the script's runtime, which apart from been undesired, will slow down the process even more.