My Favorite Bugs: Invalid Surrogate Pairs
A rare and elusive bug in a collaborative text editor caused unsaved content to be silently lost during editing, with no clear error messages or reproducible pattern at first. The issue was eventually traced to specific emoji characters that use surrogate pairs in UTF-16 encoding, where inserting certain multi-byte emoji adjacent to each other would split a surrogate pair incorrectly. This corruption disrupted the underlying CRDT synchronization mechanism, leading to data loss upon reload.
- ▪The bug occurred in a collaborative editor using TipTap and Yjs, where edits would stop syncing silently, resulting in data loss.
- ▪It was triggered by inserting certain emoji above U+FFFF, which require surrogate pairs in UTF-16, at specific byte offsets that split the pair.
- ▪JavaScript operates on 16-bit code units by default, meaning string operations like .slice() can inadvertently break surrogate pairs if not handled carefully.
- ▪Only specific emoji and edit patterns caused the issue, making it extremely rare and difficult to reproduce.
- ▪The problem was identified when a product manager noticed it consistently occurred when editing sequences of red and green circle emoji used in status reports.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | George Mandis |
| Canonical URL | https://george.mand.is/2026/05/my-favorite-bugs-invalid-surrogate-pairs/ |
| Publication time | Sat, 16 May 2026 12:49:07 +0000 |
| Retrieval time | 2026-05-16T13:10:18.577Z |
| Last seen | 2026-05-16T13:10:18.577Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 2nEDsk2YyYK_ |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
My Favorite Bugs: Invalid Surrogate PairsMay 14th, 2026 • ~2,000 words • 8 minute readIf you're in the business of building things that run on computers long enough, I think you will eventually acquire a favorite bug story. This is a short story about mine. I've also built an interactive tool where you can explore the concepts underpinning the heart of this bug.The bug: two emoji enter, none leaveI was working on migrating a legacy editor to a more collaborative experience with my team. TipTap on top (itself a wrapper around ProseMirror), Yjs underneath handling the CRDT magic for real-time syncing. It worked well! Mostly.In our alpha/early release days, when it was still mostly internal and/or early rollout users, sometimes the editor would just stop saving your content. Silently.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at George Mandis.
Discussion
0 commentsMore from George Mandis
