musescore / musescore/MuseScore
Suppress 'crashed' state via SIGTERM handler / give option to ignore
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Your idea
This is in the way when launching files for review in MuseScore in for instance, fzf.
Give the option to either:
- Handle exit state differently aka
In theory the SIGTERM handler could choose to suppress that handling - Give the option to ignore the 'crash' state and don't try to recover if a certain argument is passed or globally a checkbox is checked
Problem to be solved
When importing a file, MuseScore state may be at 'modified'.
When a user then quits the application, logs off or reboots, then the application is in 'crashed' state.
Upon next startup, there will be a annoying popup.
Prior art
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the SIGTERM handler and the logic that records the application as crashed after importing a modified file. Then inspect the startup recovery flow and define whether completion means suppressing that state on termination, adding an option to ignore it, or both; the issue does not name files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100