Skip to content
PIER
EN

Pier 0.1.52: Main-thread blocking before a freeze is now logged

Pier 0.1.52 (2026-10-26) is released. This version includes the following updates.

Changes

  • Main-thread blocks before a hang are now recorded. Main-thread tasks longer than 200 ms are immediately persisted as standalone breadcrumbs; for consecutive occurrences, only the most recent few are kept and their counts are merged, so when the app hangs you can see “who was occupying the main thread.” Each record also includes UI CPU and memory readings from the main side, to help determine whether resources were climbing before the hang.
  • The sampling budget for unresponsive diagnostics has been increased. Sampling duration is extended from 1 second to 3 seconds, and total wait from 2 seconds to 6 seconds; previously, when a process was stuck in GC, the sampler could be terminated before it even attached, leaving an empty stack file. The sampler’s error output is now recorded separately, making it easier to distinguish “sampling too slow” from “no permission to sample.”

Fixes

  • ⌘W closes the tab you are working in. When keyboard focus is on a tab, ⌘W closes that tab, not the adjacent selected tab; when blocking overlays such as the command palette, settings, or confirmation dialogs are open, ⌘W no longer closes the panel or window behind the overlay. After clicking a control that does not move keyboard focus, ⌘W also no longer closes the previous panel.
  • Windows that recover and then hang again within the sampling window are still rescued. Previously, a single “recovered” event was treated as the end of the current unresponsive handling, and a window that hung again during sampling would be left frozen; now the decision is based on whether the window is still unresponsive at the end of sampling. Multiple unresponsive episodes for the same window are also processed serially, instead of sampling in parallel and splitting the same incident into two.
  • When the UI hangs, a nonexistent stack file is no longer treated as success. The sampler still exits normally when it cannot write a file; previously this was incorrectly recorded as “stack saved.” Now success is based on whether a file actually exists on disk, and if the file cannot be written, it is recorded as a failure.