FTV is resolving a crash bug right now. And I’ve found a way to crash Gramps with a gramplet I’m beta testing. (Related to Configure settings having an out-of-range value. )
Both will immediate re-crash gramps if you break the lock and reload the same tree. (And the current view settings are likely to immediately crash again if you load any tree.)
Could Gramps have a more user-friendly recovery option than Safe Mode or hand-editing the gramps.ini view setting?
Perhaps an option to reset ALL the sidebars, bottombars, dashboard and view modes to default when the crash recovery or locked tree warning appears?
What if it just defaults back to the Dashboard. And maybe if the crash happened while in the Dashboard, then clear all attached gramplets/addons.
Yes, the user may still have an issue in one of the other views and its addons/gramplets. But getting back into the database using the dashboard eases a user’s mind that the database is safe and then the user can seek guidance in ways to back the offending addon out of a view.
I would hate to lose all of my views’ config settings.
Maybe a GUI option in the warning dialog to Restart Gramps in safe mode?
Users experience crashes extremely rarely. They may not even know that they have that option. They are unlikely to choose Safe Mode the 1st time through, but after a re-crash, they might be growing desperate.