Edition of Saturday 14 November 2026

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

Comments on “A 27-byte telemetry response nobody reads freezes Claude Desktop every two days”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

A developer traced recurring Claude Desktop freezes on Linux to a 27-byte reply to a presence-clear request that the app never reads. Chromium's no-store handling leaves each unread body in a 2 MiB shared-memory pipe holding a file descriptor. The renderer's soft limit is 1024, so after roughly a thousand replies, IPC messages stall. Chromium's bug owner calls this intended behavior. The author's repro stalls at about 900 fetches in several Chrome versions, though the claims lack independent verification.

Read the original at blog.dfb.sh. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 11 of 123 with a score of 0.67. The panel rated it highest on technical depth (0.98) and substantiated (0.94), lowest on significance (0.50). Placed No. 11, No. 16 by score alone: the placement terms moved other stories past it.

AI judgeJudge 2claude-haiku-5-5
Detailed, well-evidenced debugging writeup of a Chromium fd-exhaustion freeze in Claude Desktop, with reproducible repro and bug-tracker links. Narrow audience but high technical depth and novelty; significance moderate.
AI judgeJudge 3gpt-5.6-luna
A deeply evidenced, reproducible Chromium/Electron failure analysis with code, internals, measurements, cross-browser comparison, and a practical workaround. It is highly useful to desktop/web engineers, though its impact is narrower than a platform-wide development.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.67total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.50
  • Reader interest0.83
  • Audience breadth0.53
  • Practical relevance0.72
  • Substantiated0.94
  • Technical depth0.98
  • New information0.88
  • Counts against: Promotional0.03
  • Counts against: Overclaim0.27

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.530.350.620.500.27+0.24+0.120
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.760.800.920.830.16+0.26+0.215
Audience breadthHow many people who build technology does it concern?0.620.500.480.530.14+0.13+0.069
Practical relevanceHow useful is it to someone who builds software or tech products?0.800.550.800.720.25+0.22+0.158
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.990.900.920.940.09+0.05+0.047
Technical depthHow technically substantive is it?1.000.950.980.980.05+0.05+0.049
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.850.900.900.880.05+0.05+0.044
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.030.050.020.030.03−0.19−0.006
OverclaimDo the headline or conclusions claim more than the body supports?0.360.200.240.270.16−0.11−0.029
Sum of contributions+0.666
Claim-check penalty0.000
Total, as published0.666

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #11 on Rubric, 14 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-14/11/"><img src="https://rubric.hrih.si/badge/2026-11-14/11.svg" alt="Ranked #11 on Rubric, 14 Nov 2026" width="245" height="28"></a>

Claim check

Claim check: 4 no source given · 4 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. Couldn’t checkQuote

    Chromium's bug tracker has an open issue, assigned and P3, titled 'fetch() API will cause FD leak when request no-empty response with no-store', and its owner replied that this is working as intended.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “If you can read the Response, but choose not to, I think this is working as intended. The browser cannot know that you won't read the response in future, so…”

    The source says

    No passage could be compared.

    Source cited by the article: issues.chromium.org/issues/378822137

  2. Couldn’t checkVersion

    Chromium fixed the freeze under file descriptor exhaustion in Chrome 154 with the commit 'Reland "Make Mojo fail more predictably under FD exhaustion"'.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “The leak is intended, but the freeze at exhaustion was a bug, and Chromium fixed it in Chrome 154”

    The source says

    No passage could be compared.

    Source cited by the article: github.com/chromium/chromium/commit/0ce1bca2693a03bcee73f839c3e63b38ff5693f9

  3. Couldn’t checkDate

    Chromium closed the author's bug 582417463, which asked for fetch() to reject with a TypeError, on the same day as a duplicate of 378822137.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “Chromium closed it the same day as a duplicate of 378822137”

    The source says

    No passage could be compared.

    Source cited by the article: issues.chromium.org/issues/582417463

  4. Couldn’t checkQuote

    A bot closed the author's Claude Desktop issue in the claude-code repository as invalid, saying it does not appear to be about Claude Code, and no human replied.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “Closing for now — this doesn't appear to be about Claude Code”

    The source says

    No passage could be compared.

    Source cited by the article: github.com/anthropics/claude-code/issues/107887

  5. No source givenCausal conclusion

    Claude Desktop on Linux freezes because 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 descriptors.

    The article gives no link or citation for it.

    The article says

    “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”

    The source says

    No source to compare with.

  6. No source givenNumber

    In the core dump, 938 of 942 shared-memory regions held only the 27-byte reply {"refresh_after_seconds":0}.

    The article gives no link or citation for it.

    The article says

    “The dump had 942 such regions, and 938 of them contained only this”

    The source says

    No source to compare with.

  7. No source givenNumber

    The renderer's soft RLIMIT_NOFILE is 1024, while the browser process raises its own to 524288.

    The article gives no link or citation for it.

    The article says

    “The renderer's soft RLIMIT_NOFILE is 1024, while the browser process raises its own to 524288”

    The source says

    No source to compare with.

  8. No source givenBenchmark result

    With the response body cancelled, the Electron 44.9.3 repro finishes all 1100 requests at 38 descriptors, whereas without it the page stops.

    The article gives no link or citation for it.

    The article says

    “With the body cancelled, the Electron 44.9.3 repro finishes all 1100 requests at 38 descriptors, and without it the page stops”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 2 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 15 Nov 2026, 20:44 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “A 27-byte telemetry response nobody reads freezes Claude Desktop every two days”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.

  1. Score 0.67

    Semver Trick