unsnooze 1.16.2 → 1.16.3

package/CHANGELOG.md

@@ -1,5 +1,31 @@
 # Changelog
 
+## 1.16.3 — 2026-08-22
+
+- **A dashboard left open overnight no longer runs the machine out of memory.**
+  ([#16](https://github.com/saaranshM/unsnooze/issues/16)) `unsnooze status` in
+  a spare pane is exactly what it is for, and after nine or ten hours it was
+  dying on *"FATAL ERROR: Ineffective mark-compacts near heap limit — JavaScript
+  heap out of memory"*. The dashboard itself was innocent: React's development
+  build files a `performance.measure()` entry for every render, commit and
+  `setState` — the performance track it publishes for devtools — and Node
+  buffers user-timing entries forever with nothing to drain them. The status tab
+  repaints about three times a second (a one-second data tick plus the
+  450ms logo animation), each repaint left roughly 40 entries behind, and a
+  night of that walks into Node's 2GB heap ceiling. Measured at ~12kB retained
+  per render, surviving a forced garbage collection. The dashboard now drains
+  that buffer while it is mounted; heap use went from climbing without limit to
+  flat. Nothing else in unsnooze records user timing, and no other command
+  renders long enough to have been affected.
+
+- **Every release now creates its GitHub release automatically.** They were
+  written by hand afterwards, so 1.16.2 shipped to npm and to the website while
+  the repository's Releases tab still showed 1.16.1. The publish workflow now
+  creates the release from that version's CHANGELOG section, and waits for the
+  npm registry to actually serve the new version before rebuilding the website —
+  `npm publish` returns before the registry does, which is why 1.16.2's own
+  changelog entry was briefly invisible on unsnooze.dev.
+
 ## 1.16.2 — 2026-08-22
 
 - **A herdr revival now opens a tab in your project's workspace, not a new

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "unsnooze",
-  "version": "1.16.2",
+  "version": "1.16.3",
   "description": "Automatically resume Claude Code, Codex CLI, Grok, Qwen Code, Kimi CLI, OpenCode, and Antigravity sessions when 5-hour or weekly usage limits reset—on macOS, Linux and Windows, with or without a terminal multiplexer.",
   "keywords": [
     "claude",

package/src/dashboard/run.js

@@ -62,6 +62,41 @@ export function installMouseCleanup(stdout = process.stdout) {
   };
 }
 
+// React's development build records a `performance.measure()` entry for every
+// render, commit and setState — the React Performance Track it publishes for
+// devtools. Node buffers user-timing entries and nothing ever drains that
+// buffer, so on a long-lived dashboard it IS the leak: the status tab repaints
+// roughly three times a second (a 1s data tick plus the 450ms logo animation),
+// each repaint leaves ~40 entries behind, and an overnight `unsnooze status`
+// walked into Node's 2GB heap ceiling and aborted (#16). Measured at ~12 kB
+// retained per render, surviving a forced GC.
+//
+// The entries cannot be capped (Node caps resource timing, not user timing) and
+// switching React to its production build would mean setting NODE_ENV for the
+// whole CLI before anything imports React. Draining is the narrow fix: nothing
+// in unsnooze reads user timing, and the sweep lives exactly as long as the
+// render does.
+export const TIMING_SWEEP_MS = 5_000;
+
+export function sweepReactTiming(perf = globalThis.performance) {
+  try {
+    perf?.clearMeasures?.();
+    perf?.clearMarks?.();
+  } catch { /* a runtime with no user timing has nothing to leak */ }
+}
+
+// Returns the stop function. The timer is unref'd: draining a buffer is never
+// a reason to hold the process open.
+export function startTimingSweep({ intervalMs = TIMING_SWEEP_MS, perf } = {}) {
+  sweepReactTiming(perf);
+  const timer = setInterval(() => sweepReactTiming(perf), intervalMs);
+  timer.unref?.();
+  return () => {
+    clearInterval(timer);
+    sweepReactTiming(perf);
+  };
+}
+
 export function shouldUseDashboard({
   force = null,
   json = false,
@@ -87,13 +122,18 @@ export async function runDashboard({ tab = 'status' } = {}) {
   }
 
   installMouseCleanup(process.stdout);
-  const instance = render(h(App, { initialTab: tab, mouseEnabled: getConfig('mouse') !== false }), {
-    exitOnCtrlC: true,
-    // Full-screen: separate buffer like vim / htop / less — original scrollback restored on quit
-    alternateScreen: true,
-  });
+  const stopTimingSweep = startTimingSweep();
+  try {
+    const instance = render(h(App, { initialTab: tab, mouseEnabled: getConfig('mouse') !== false }), {
+      exitOnCtrlC: true,
+      // Full-screen: separate buffer like vim / htop / less — original scrollback restored on quit
+      alternateScreen: true,
+    });
 
-  await instance.waitUntilExit();
+    await instance.waitUntilExit();
+  } finally {
+    stopTimingSweep();
+  }
   // Belt and braces: normal quit also clears modes (provider already did).
   process.stdout.write(MOUSE_DISABLE_ALL);
   return 0;