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

**URL:** <https://forum.devtalk.com/t/a-27-byte-telemetry-response-nobody-reads-freezes-claude-desktop-every-two-days/251715>\
**Category:** AI In The News\
**Tags:** via-news-bot, claude, telemetry, in-the-news, desktop\
**Created:** [14 November 2026 19:23 UTC](https://forum.devtalk.com/t/a-27-byte-telemetry-response-nobody-reads-freezes-claude-desktop-every-two-days/251715 "2026-11-14T19:23:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![CommunityNews](https://forum.devtalk.com/user_avatar/forum.devtalk.com/communitynews/32/1113_2.png) [@CommunityNews](https://forum.devtalk.com/u/CommunityNews)\
**Post date:** [14 November 2026 19:23 UTC](https://forum.devtalk.com/t/a-27-byte-telemetry-response-nobody-reads-freezes-claude-desktop-every-two-days/251715/1 "2026-11-14T19:23:01Z")

</div>

> Claude Desktop on Linux froze dead every couple of days, with empty logs. It took two months and a 1.5 TiB core dump to find out why. The app never reads a 27-byte telemetry reply, and Chromium keeps a file descriptor open for each one until the renderer runs out of them. Chromium says it works as intended, and Anthropic’s bot closed my issue as “not about Claude Code”.

Read in full here:

> **[A 27-byte telemetry response nobody reads freezes Claude Desktop every two days](https://blog.dfb.sh/blog/claude-desktop-freeze/)**
>
> Claude Desktop on Linux froze dead every couple of days, with empty logs. It took two months and a 1.5 TiB core dump to find out why. The app never reads a 27-byte telemetry reply, and Chromium keeps a file descriptor open for each one until the...