Closing SavePoint while a snapshot is running leaves a stopped git process behind #127
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ethan-hann/SavePoint#127
Loading…
Reference in a new issue
No description provided.
Delete branch "%!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?
On Linux (Ubuntu 26.04 GNOME, Wayland, AppImage 0.9.9) I started a snapshot of a game folder with 400,000 empty files, so two snapshot jobs were running, and closed the window with the X. The window closed without a question and both jobs ended as cancelled (log: "Cancelled: Capture ... error.capture.cancelled"). After that a
git ls-files -z -o --exclude-from=.../install.git/info/excludeprocess from the bundled git was still there in state T (stopped), owned by init, started one second before the exit, and the AppImage launcher process and its/tmp/.mount_SavePo...mount stayed too until I killed them by hand. Expected: no process of SavePoint's own left after the app exits, and the mount gone. Evidence:psshowed PID of git with STAT T, PPID 1; session log lines at 05:38:39. To check: whether the cancel stops the child (SIGSTOP) but never ends it, and whether quitting should ask first when a snapshot is more than a minute in.Found in the Linux desktop checks (#3).