Hi everyone, Since 1.6.0 was released, we've seen a relatively high number of reports about Mixxx crashing on start-up. A large number of these are solved by deleting .mixxx.cfg, and others .mixxxtrack.xml, which tells us that we're either writing invalid config files or library XML.
I suspect a big source of headaches is the numerous ways in which you can break the library's XML. My gut feeling is that UTF-8/UTF-16 strings are causing problems for users who have libraries which includes a lot of non-Western music. It's way too late in the development phase to try to tackle ANY of these potentially library-related crashes on startup, and IMO the effort would be better spent working on the sqlite-based library instead anyways. (The old library code is very, very deep rabbit hole.) However, I'm wondering if we should try to add a workaround for these problems by detecting if Mixxx has failed to launch, and offering the user an option to clear their library/settings files. We can pull this off by implementing a very simple lockfile. I don't know if this is just a waste of time though, because it's essentially a cheap hack to deal with buggy code and the users that get Mixxx to work through this won't be able to save their libraries (since they'll have the same problem on every run), and I just don't know how users would react. Anyone care to chime in? Thanks, Albert ------------------------------------------------------------------------------ _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
