The footprint command’s current physical-footprint value.
Measured footprint
Light is a claim.
Here is the reading.
Linelark is meant to live in the Dock and remain open through the day. This is the first public snapshot from a real long-running session—not a best-case laboratory number.
Physical footprint≈70MBObserved after 2 h 34 min
Snapshot 001
A working session,
not an empty launch.
Recorded 26 August 2026. The app had already been running for 2 h 34 min. Memory varies with files, panes, syntax state, plugins, and live terminals.
The visible Memory-column reading supplied with the same session.
The session’s peak—not its steady observed value.
Long enough to represent the “leave it open” use case.
- Release
- Studio 1.0
- Machine
- Apple M5 Pro · 24 GB
- System
- macOS 26.5.2
- Artifact
- 4.9 MB universal DMG
Method and limits
Reproducible,
with the caveat attached.
The screenshot was read in Activity Monitor’s Memory tab. The same running process was then checked with Apple’s command-line footprint tool, which reported 70.3 MB current and 106.7 MB peak physical footprint.
pid=$(pgrep -x Linelark)
footprint "$pid"This is an observed creator session, not a controlled comparison against another editor. It does not establish cold-start time, energy use, or a universal memory ceiling. Those require a repeatable workload and will be added only after that protocol exists.
Why the baseline stays small
The app brings an editor,
not a browser engine.
Native controls, windows, menus, and text infrastructure.
No continuous project indexer running simply because a folder is open.
Terminals and plugin work appear when the workflow asks for them.