Bitwarden Shipped My Fix

Thu, 03 Sep 2026 07:30:00 +0000

Back in August I wrote about my self hosted Bitwarden server falling over during a routine update. If you missed it, that post is here.

Quick recap: the update died about halfway through, after it had stopped all my containers but before it had touched any of my data. The stack trace pointed into Bitwarden’s own source rather than anything I had misconfigured. Their setup helper was writing to a single StringBuilder from two threads at once, one handling normal output and one handling errors. Most of the time those two don’t collide. On that particular version they collided nearly every run, which is why the update failed so reliably for me and worked fine for plenty of other people. The fix was a lock around both handlers, about four lines, and it was merged into main six days later.

Using AI to Find and Fix a Real Bug in Bitwarden

Mon, 17 Aug 2026 10:00:00 +0000

I run my own self-hosted Bitwarden server. It holds every password I have, so I keep it patched and don’t take chances with it. A couple of weeks ago, gone 9pm, about to call it a day, a routine update went sideways: a crash, a couple of hours hunched over a stack trace in someone else’s source code, and eventually a pull request against Bitwarden’s official repository fixing a genuine bug.

Bitwarden on cttech.io

Bitwarden Shipped My Fix

Using AI to Find and Fix a Real Bug in Bitwarden