identify memory leaks. Attempt 4

Author: maslianok

.github/workflows/deploy.yml

@@ -76,6 +76,7 @@ jobs:
               -e AUTH_URL='${{ vars.AUTH_URL }}' \
               -e AUTH_TRUST_HOST=true \
               -e NEXT_PUBLIC_URI='${{ vars.NEXT_PUBLIC_URI }}' \
+              -e HEAP_SNAPSHOT_TOKEN='${{ secrets.HEAP_SNAPSHOT_TOKEN }}' \
               -p 3000:3000 \
               -p 127.0.0.1:9229:9229 \
               ghcr.io/gitranks/gitranks-ui:latest

app/api/_debug/heap/route.ts

@@ -0,0 +1,14 @@
+import { writeHeapSnapshot } from '@/utils/heap-snapshot';
+import { NextResponse } from 'next/server';
+
+export async function GET(request: Request) {
+  const url = new URL(request.url);
+  const token = url.searchParams.get('token');
+
+  if (token !== process.env.HEAP_SNAPSHOT_TOKEN) {
+    return new NextResponse('Forbidden', { status: 403 });
+  }
+
+  const file = writeHeapSnapshot();
+  return NextResponse.json({ file });
+}

utils/heap-snapshot.ts

@@ -0,0 +1,8 @@
+import v8 from 'v8';
+
+export function writeHeapSnapshot() {
+  const file = `/tmp/heap-${Date.now()}.heapsnapshot`;
+  v8.writeHeapSnapshot(file);
+  console.log('Heap snapshot saved:', file);
+  return file;
+}