hn.today

A 27-byte telemetry response nobody reads freezes Claude Desktop every two days

blog.dfb.sh9 points1 comments
Screenshot of A 27-byte telemetry response nobody reads freezes Claude Desktop every two days

Claude Desktop on Linux, an Electron app, repeatedly froze or lost its renderer after running for a day or two, often without useful logs. The investigation took two months of instrumentation and culminated in capturing a live renderer’s memory. Crashes also triggered enormous core dumps: Chromium reserves about 1.5 TiB of virtual address space, largely for V8’s sandbox, and the renderer’s security policy prevents V8 from marking that reservation as excluded from dumps. A sparse-file-aware search tool made it practical to inspect the dump without reading terabytes of empty space.

The memory revealed the renderer was waiting for a reply from Chromium’s browser process. The reply had arrived, but sat behind another message: a tiny, 27-byte response to a telemetry presence request that the app never reads. The response’s cache-control behavior led Chromium to retain a file descriptor for each such response; repeated requests gradually exhausted the renderer’s descriptor limit and left the app frozen or dead. The account reports reproducing the problem without Claude, and says Chromium considers the behavior working as intended. A newer Chrome version did not resolve it, while Anthropic’s issue bot closed the report as unrelated to Claude Code. The findings point to an interaction between an unread telemetry response, Chromium’s handling of non-cacheable response bodies, and an application that stays open for days.

Read on blog.dfb.sh1 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Web

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.