BriskEdit 0.3.4

Release Notes

0.3.4 — ⛔️ Critical Fix: Formatter memory safety hardening

A critical stability release on top of 0.3.3. Still an unsigned developer preview — on
first launch, right-click BriskEdit.app → Open → confirm.

Fixed

• Fixed the remaining Format Document memory runaway. Clang-format project
  configuration discovery now uses a bounded, cycle-safe lexical parent walk
  instead of an unbounded Foundation URL loop.
• All formatter entry points now share one global single-flight gate, including
  manual formatting and format-on-save.
• Formatter processes now have strict input, output, and execution-time limits;
  stdout and stderr are drained concurrently to prevent pipe deadlocks.
• Stale format-on-save results are discarded when the document changes before
  formatting completes.

Improved

• Git, diagnostics, tool discovery, and installer processes now use bounded
  output capture and timeouts.
• Oversized editor files, LSP messages, Discord IPC frames, Markdown previews,
  and search buffers are capped to keep memory use predictable under malformed
  or unexpectedly large input.
• Formatter telemetry now records duration, input size, and suppressed duplicate
  requests for future incident diagnosis.

Compatibility

Requires macOS 26 or newer. Xcode 26+ to build from source.