The footprint command’s current physical-footprint value.
Measured footprint
What Linelark actually
uses in memory.
Linelark is meant to sit in the Dock and stay open through the day. This is the first public reading, taken from a real session rather than a best-case launch.
Physical footprint≈70MBObserved after 2 h 34 min
Snapshot 001
Recorded after a full session.
Taken 26 August 2026, with the app already running for 2 h 34 min. Memory varies with open files, panes, syntax state, plugins, and live terminals.
The visible Memory-column reading supplied with the same session.
The highest point of the session, not its steady value.
Long enough to stand for leaving the app open all day.
- Release
- Studio 1.0
- Machine
- Apple M5 Pro · 24 GB
- System
- macOS 26.5.2
- Artifact
- 8.7 MB universal DMG
Method and limits
How it was measured.
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 one observed session on my own Mac, not a controlled comparison with another editor. It says nothing about cold-start time, energy use, or a memory ceiling. Those need a repeatable workload, and they will go up here once that exists.
Architecture
There is no browser engine inside.
Native controls, windows, menus, and text handling.
Opening a folder does not start an indexer that keeps running.
Terminals and plugins start when you ask for them.