From f516baa0aa97d1574ddecd7399b05e5ea7d8720a Mon Sep 17 00:00:00 2001
From: Claude Bot <claude-bot@bun.sh>
Date: Tue, 25 Nov 2025 06:40:19 +0000
Subject: [PATCH] test: add regression test for issue #11680
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Add regression test to verify that the floating point exception (SIGILL)
that occurred on macOS in os.loadavg() no longer happens.

The issue was caused by division by zero when the system's fscale value
was 0. This was fixed in commit 731a85f80d (June 8, 2024) by adding
zero-check guards before division in src/bun.js/node/node_os.zig.

The test verifies:
1. os.loadavg() returns valid finite numbers without crashing
2. DNS resolution with socket connections works without floating point errors

Fixes #11680

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
---
 test/regression/issue/11680.test.ts | 56 +++++++++++++++++++++++++++++
 1 file changed, 56 insertions(+)
 create mode 100644 test/regression/issue/11680.test.ts

diff --git a/test/regression/issue/11680.test.ts b/test/regression/issue/11680.test.ts
new file mode 100644
index 0000000000..eaac35f67b
--- /dev/null
+++ b/test/regression/issue/11680.test.ts
@@ -0,0 +1,56 @@
+// Regression test for issue #11680
+// https://github.com/oven-sh/bun/issues/11680
+//
+// This issue caused a floating point exception (SIGILL) on macOS when running
+// long-lived processes like `nuxt dev`. The crash occurred in os.loadavg() when
+// the system's fscale value was 0, causing division by zero.
+//
+// Fixed in commit 731a85f80d (June 8, 2024) by adding zero-check guards
+// before division in the load average calculation.
+
+import { expect, test } from "bun:test";
+import { connect } from "node:net";
+import os from "node:os";
+
+test("os.loadavg() should not crash with floating point error", () => {
+  // This should not throw a floating point exception even on systems
+  // where fscale might be 0 (macOS-specific edge case)
+  const loadavg = os.loadavg();
+
+  expect(loadavg).toBeArrayOfSize(3);
+  expect(loadavg[0]).toBeNumber();
+  expect(loadavg[1]).toBeNumber();
+  expect(loadavg[2]).toBeNumber();
+
+  // All values should be finite (not NaN or Infinity)
+  expect(Number.isFinite(loadavg[0])).toBe(true);
+  expect(Number.isFinite(loadavg[1])).toBe(true);
+  expect(Number.isFinite(loadavg[2])).toBe(true);
+});
+
+test("DNS resolution with socket connection should not crash", async () => {
+  // The original issue occurred during DNS resolution + socket connection
+  // in a long-running Nuxt dev server
+  await new Promise<void>((resolve, reject) => {
+    const socket = connect({
+      host: "example.com",
+      port: 80,
+      timeout: 5000,
+    });
+
+    socket.on("connect", () => {
+      socket.end();
+      resolve();
+    });
+
+    socket.on("error", err => {
+      // Connection errors are fine - we're testing that it doesn't crash
+      resolve();
+    });
+
+    socket.on("timeout", () => {
+      socket.destroy();
+      resolve();
+    });
+  });
+});