1 files changed, 68 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/1687 b/results/classifier/zero-shot/108/other/1687
new file mode 100644
index 000000000..f7c28e995
--- /dev/null
+++ b/results/classifier/zero-shot/108/other/1687
@@ -0,0 +1,68 @@
+graphic: 0.840
+device: 0.833
+PID: 0.726
+semantic: 0.651
+permissions: 0.603
+debug: 0.560
+vnc: 0.552
+performance: 0.476
+socket: 0.329
+network: 0.311
+boot: 0.128
+files: 0.102
+other: 0.044
+KVM: 0.042
+
+Memory leak for x86 guest on macOS ARM host
+Description of problem:
+QEMU is used by docker to run `x86` binaries on Apple silicon. Then using `mmap` followed by `munmap` results in a memory leak manifested by continuously growing RSS memory usage when running `mmap` and `munmap` in a loop, e.g., when running the following binary:
+
+```
+#include <stdio.h>
+#include <unistd.h>
+#include <sys/mman.h>
+
+const int page = 4096;
+
+int work(int N) {
+  int *ptr = mmap(NULL, N * sizeof(int), PROT_WRITE, MAP_PRIVATE | MAP_ANONYMOUS, 0, 0);
+
+  if (ptr == MAP_FAILED) {
+    printf("Mapping Failed\n");
+    return 1;
+  }
+
+  for(int i = 0; i < N; i++) {
+    ptr[i] = i * 10;
+  }
+
+  int err = munmap(ptr, N * sizeof(int));
+  if (err != 0) {
+    printf("UnMapping Failed\n");
+    return 1;
+  }
+
+  return 0;
+}
+
+int main() {
+  int N = page * 1024;
+
+  while (1) {
+    int res = work(N);
+    if (res) {
+      return res;
+    }
+    printf(".\n");
+  }
+
+  return 0;
+}
+```
+Steps to reproduce:
+```
+$ LEAK=$(docker run --platform linux/amd64 -d -it martin2718/mmap-leak ./a.out)
+$ docker exec -it $LEAK top        # you should observe that RES for a.out keeps growing
+$ docker exec -it $LEAK pmap -x 1  # you should see a single memory mapping whose RSS memory usage keeps growing
+$ docker kill $LEAK                # abort the experiment
+```