blog · release

bunqueue v2.0.9

Fixes 4 bugs and ships 1 addition. Critical: Memory leak in EventsManager - Cancelled waiters in waitForJobCompletion() were never removed from the completionWaiters map on timeout.

egeominotti

To install bunqueue v2.0.9

bun add bunqueue@2.0.9

npm install bunqueue@2.0.9

To upgrade bunqueue

bun add bunqueue@latest

What’s new

• Comprehensive test suites for all bug fixes:
  • test/bug-memory-leak-waiters.test.ts - 5 tests verifying memory leak fix
  • test/bug-lost-notification.test.ts - 4 tests verifying notification fix
  • test/bug-writebuffer-dataloss.test.ts - 10 tests verifying WriteBuffer fix
  • test/bug-verification-remaining.test.ts - 7 tests verifying CustomId fix and JS concurrency model

Bugfixes

• Critical: Memory leak in EventsManager - Cancelled waiters in waitForJobCompletion() were never removed from the completionWaiters map on timeout. Now properly cleaned up when timeout fires.
• Critical: Lost notification TOCTOU race - Fixed race condition in pull.ts where notify() could fire between tryPullFromShard() returning null and waitForJob() being called. Added pendingNotification flag to Shard to capture notifications when no waiters exist.
• Critical: WriteBuffer data loss - Added exponential backoff (100ms → 30s), max 10 retries, critical error callback, stopGracefully() method, and enhanced error callback with retry information. Previously, persistent errors caused infinite retries and shutdown lost pending jobs.
• Critical: CustomIdMap race condition - Concurrent pushes with same customId could create duplicates. Moved customIdMap check inside shard write lock for atomic check-and-insert.

Thanks to 1 contributor!

• @egeominotti

---

← bunqueue v2.0.3 · Release on GitHub · Commits since v2.0.3 · Full changelog · All posts