NEC-312: Excalidraw hardness: a tab crash at ~677 shapes on a drawing switch (FLAKE-20) #318
No reviewers
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
dependencies
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
security
usability
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!318
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-nec-312-excalidraw-hardness-a-tab-crash-at-677-s"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Task: NEC-312 — https://projectron.nerchure.com/tasks/332
FLAKE-20, a renderer crash on a drawing switch at about 677 shapes, left no evidence: the hang watch went blind after a vault's first relaunch, and a crash's logs were read through the renderer that had died. This makes a crash report itself. It records Chromium's termination status and signal, with a host-side report (heartbeats, cgroup memory with oom_kill, processes, diag log from disk), re-arms the watch after every relaunch, samples every Obsidian process's memory once a second, and traces each vault's memory after every hardness round. A probe measures memory across drawing switches.
The seed was replayed three times with the reporting in place, once on the tree that crashed. The crash did not come back. One renderer reaches about 4 GB on a switch at the crash's size, and the container gets to within about a gigabyte of the VM's limit, which fits an OOM or a heap failure but was not observed. FLAKE-20 stays Unexplained, and now reports itself.
The replays, the probe and two fresh-context reviews found three drawing sync bugs, fixed here as ride-alongs, plus one in the container runner. The Excalidraw hardness run passed two hours on two seeds, newest against oldest, on this branch's sync path (one before NEC-340, one after); the canvas and Markdown runs had 5 minutes each to check the shared harness wiring.
Spec:
docs/changes/NEC-312-excalidraw-tab-crash/spec.mdAlso fixes NEC-337: A drawing a script wrote gets a spurious kept copy of every image on first open
Also fixes NEC-339: A vault's open drawing never draws a winning rival of the same version
Also fixes NEC-340: An edit made on a version a drawing's view went back to is lost, with no copy
Also fixes NEC-342: A container e2e run copies out an earlier run's dumps and report as its own
Changelog
An edit made to a shape just as an open drawing reloads an older version of it is no longer lost.