ci: don't check for memory leaks, use-after-free, double free

This is unfortunate, but the checker is too dumb. It also has no way to
suppress false positives, so we either have to make undesirable changes
to the code, or else disable the checker entirely.

We only really want to disable the memory leak checker, but there's no
way to do that without also disabling the check for use-after-free or
double free, so here we are.

My opinion of scan-build has declined drastically today. This is sad.
But it seems like the best we can do.

Part-of: <https://gitlab.gnome.org/GNOME/epiphany/-/merge_requests/1045>

1 files changed, 1 insertions, 1 deletions

diff --git a/.run-scan-build b/.run-scan-build
index 88fe82454..ea778b932 100755
--- a/.run-scan-build
+++ b/.run-scan-build
@@ -2,4 +2,4 @@
 
 set -e
 
-scan-build -v --status-bugs "$@"
+scan-build -v --status-bugs -disable-checker unix.Malloc "$@"