On Tue, 2021-01-05 at 09:49 +0100, Milan Crha via evolution-list wrote: [...] > one part of the preallocated memory can be a gigacage used by > WebKitGTK. It's better to disable it when running under valgrind. > My commands look like this: > > $ export GIGACAGE_ENABLED=0 > $ G_SLICE=always-malloc valgrind --show-leak-kinds=definite \ > --num-callers=30 --leak-check=full \ > --aspace-minaddr=0x100000000 evolution &>log.txt
Thanks for the tip. I tried that command (as well as my previous command but with the GIGACAGE_ENABLED=0 variable), and unfortunately I still get the same thing as before: ** WARNING **: Failed to seal memfd: Invalid argument ** WARNING **: Failed to seal memfd: Invalid argument ** ERROR **: Failed to write memfd Trace/breakpoint trap (core dumped) Any ideas what to do with that? > Make sure you've installed debuginfo packages for glib2, gtk3, > evolution-data-server and evolution at least, to get usable > backtraces. Yup, I did! _______________________________________________ evolution-list mailing list [email protected] To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
