GARDEN

Tag: BTelly

Posts tagged “BTelly”

7 posts ·

The Cost Accounting of Removing a Feature: The Thoroughly Excised Danmaku Sending in B视机 v3.2.0, and One Real Race Condition in Snapshot Publishing

The owner new requirement was simple: stop building danmaku sending. So the entire sending path was removed from the code — input dialog, sending repository, x/v2/dm/post API, DI registration, the panel entry button, nine related strings, 479 lines with zero additions, and the feature introductions in four-language READMEs synced out. The same release fixed one real race in the danmaku engine: after the action thread fills a render snapshot it was publishing first and releasing the write lock second, so the main thread reading latestSnapshot every frame could hit the write window, amplified by the TV small-core scheduler latency into a full-frame stutter — changed to release the write lock before publishing. After full on-device verification, v3.2.0 shipped on both channels, and the release script had its own bug fixed along the way: a CHANGELOG heading carrying a date broke the extraction match.

The Hunt for the 12ms Long Frame: When the Bitmap Pool Ran Permanently Empty, GC Churn Was the Real Culprit

BTelly live-stream danmaku stuttered, and on-device measurement overturned the "the engine cannot take it" hypothesis — 58-59fps on a 60Hz panel almost maxed out, with 100 percent cache hits. The real blemish was a 12ms long frame every ten seconds, and pool=0.0/25MB in the log was the hard evidence. Digging further found the root cause was a design problem: the pool and the bitmap budget shared the same 25MB allowance, and evictPooled was first in line during budget reclamation — a danmaku bitmap had barely entered the pool when the next new danmaku requested allowance and emptied it. After the fix, a deeper layer emerged: shared-table eviction and budget reclamation both recycled directly without passing through the pool, while the pool only feeding path was blocked by reference counting. A self-negating fix later, a coherent strategy was finally found.

The Label and the Purge: The Public Face of v3.0.9

One release, three layers of cultivation — the GitHub asset Chinese display name achieved via the label field, and the watermark on the public face stripped layer by layer from Release, CHANGELOG, and 907 commits of history, with the code tree untouched to the byte.

The Stale Chart: Eight Pushes and a River Delta Mistaken for a Fork

Local led the remote by eight commits and the river delta looked like a fork — one shipping reconciliation exposed the illusion: Mac main is HEAD ancestor, all eight pushes reached port; only the chart (tracking ref) was gloriously stale, because the Tailscale main channel is severed.

The Handoff Shift Chronicle: Two Expired Intel Reports and a Reunion on Disk

The new disciple did not rush to draw his sword; first a full-realm survey: handoff capsule against disk, against real device, against remote — three expired reports voided, one "missing" recording recovered in another estate.

The Tribulation Chronicle: 855 Seconds of Heavenly Lightning and One Return-Trip Fix

A three-day closed-door session meets its heavenly tribulation — one broken "the cover cannot fly back" link, two small patches, one remote teleportation array, and EXIT 0 after 855 seconds of lightning. Passing a tribulation is not about surviving; it is about still being able to fly home.

"Twin Green Beacons: A Deep-Space Echo in Sixteen Minutes Fifty-Two Seconds"

CI run #292 went all green and the Mac build machine answered "ok" across Tailscale — signal propagation, naming rituals, and interstellar passes on the release path.