GSOC 2018: User Action Logger

My primary concern about being able to make this happen is that very often the crash leads to a score becoming filled with blanks. What is to prevent this from happening with the User Action Logger as well? Since I know of no programmer who has experienced this, no one knows what causes the crash and corruption. Is the problem with QT? Is it in the C++ code in MuseScore? I realize that once this feature is tested, that is some unsuspecting user has a MuseScore crash that leads to this corruption, no one will know for sure which library is causing the issue. The log will either be empty or show the actions the user was taking when the crash occurred. I would also have this feature track preferences, such as language and auto save status. My suspicion is that this corruption is caused when auto save kicks in at the same time as some other, as yet unknown, event.

By the way, this is a very badly needed feature. These crashes are unacceptable and I'm optimistic that this catastrophic event will be fixed once and for all.

Just some thoughts.