Segmentation fault at "normalizeName(name) == name"

[nik.martin]

I ran mix for about an hour, making a new playlist, I exited normally, then when I tried to restart, I get:

Critical [Main]: DEBUG ASSERT: "normalizeName(name) == name" in function void DbNamedEntity<T>::setName(const QString&) [with T = CrateId] at src/util/db/dbnamedentity.h:25
Segmentation fault (core dumped)

And mixxx exits. I assume this is related to something in the database, but I'm not sure how to fix it.

[nik.martin (nik-martin)]

Here is the relevant portion of the same sequence with mixxx --developer:

Info [Main]: DbConnection - Available drivers for database connections: ("QIBASE", "QSQLITE", "QMYSQL", "QMYSQL3", "QODBC", "QODBC3", "QPSQL", "QPSQL7", "QTDS", "QTDS7")
Debug [Main]: DbConnection - Opening database connection "MIXXX-1" QSqlDatabase(driver="QSQLITE", database="/home/nmartin/.mixxx/mixxxdb.sqlite", host="localhost", port=-1, user="mixxx", open=false)
Info [Main]: DbConnectionPool - Cloned thread-local database connection "MIXXX-1" QSqlDatabase(driver="QSQLITE", database="/home/nmartin/.mixxx/mixxxdb.sqlite", host="localhost", port=-1, user="mixxx", open=true)
Info [Main]: MixxxMainWindow - Connecting to database
Debug [Main]: DbConnectionPooled - Found thread-local database connection "MIXXX-1" QSqlDatabase(driver="QSQLITE", database="/home/nmartin/.mixxx/mixxxdb.sqlite", host="localhost", port=-1, user="mixxx", open=true)
Info [Main]: MixxxMainWindow - Initializing or upgrading database schema
Info [Main]: SchemaManager - Database schema is up-to-date at version 28
Debug [Main]: LibraryScanner - Starting thread
Debug [Main]: DbConnectionPooled - Found thread-local database connection "MIXXX-1" QSqlDatabase(driver="QSQLITE", database="/home/nmartin/.mixxx/mixxxdb.sqlite", host="localhost", port=-1, user="mixxx", open=true)
Info [Main]: Library - Connecting database
Debug [LibraryScanner 1]: LibraryScanner - Entering thread
Debug [LibraryScanner 1]: DbConnection - Opening database connection "MIXXX-2" QSqlDatabase(driver="QSQLITE", database="/home/nmartin/.mixxx/mixxxdb.sqlite", host="localhost", port=-1, user="mixxx", open=false)
Info [LibraryScanner 1]: DbConnectionPool - Cloned thread-local database connection "MIXXX-2" QSqlDatabase(driver="QSQLITE", database="/home/nmartin/.mixxx/mixxxdb.sqlite", host="localhost", port=-1, user="mixxx", open=true)
Debug [LibraryScanner 1]: DbConnectionPooled - Found thread-local database connection "MIXXX-2" QSqlDatabase(driver="QSQLITE", database="/home/nmartin/.mixxx/mixxxdb.sqlite", host="localhost", port=-1, user="mixxx", open=true)
Debug [Main]: Committing transaction on "MIXXX-1" result: true
Debug [LibraryScanner 1]: LibraryScanner - Event loop starting
Debug [Main]: CrateFeature::rebuildChildModel() -1
Critical [Main]: DEBUG ASSERT: "normalizeName(name) == name" in function void DbNamedEntity<T>::setName(const QString&) [with T = CrateId] at src/util/db/dbnamedentity.h:25
Debug [Main]: Default quick links: ("/run/media/nmartin/6abc4643-4cef-4dc6-b8e2-f30d4c99ca19/DJLib/", "/home/nmartin/Music/", "/home/nmartin/Downloads/", "/home/nmartin/Desktop/", "/home/nmartin/Documents/")
Debug [Main]: Appending Quick Link: "DJLib" --- "/run/media/nmartin/6abc4643-4cef-4dc6-b8e2-f30d4c99ca19/DJLib/"
Debug [Main]: Appending Quick Link: "Music" --- "/home/nmartin/Music/"
Debug [Main]: Appending Quick Link: "Downloads" --- "/home/nmartin/Downloads/"
Debug [Main]: Appending Quick Link: "Desktop" --- "/home/nmartin/Desktop/"
Debug [Main]: Appending Quick Link: "Documents" --- "/home/nmartin/Documents/"
Debug [Main]: Committing transaction on "MIXXX-1" result: true
Debug [Main]: Found "Traktor 2.11.2"
Debug [Main]: Trakt...

[nik.martin (nik-martin)]

I have seen this same error in the past, and it was after I updated my OS (Arch Linux), and it required a rebuild of mixx from source.Why would/should an OS update break an app?

[Uwe Klotz (uklotzde-deactivatedaccount)]

Your database seems to contain crate names with leading or trailing white spaces. Mixxx should prevent that entries with invalid names are created.

This is just a debug assertion to detect unexpected anomalies in existing databases during development. The release version should not be affected when using the correct build settings and command line args.

[Daniel Schürmann (daschuer)]

Shouldn’t we give here a more explicit error message, that the user has the chance to fix this via a db tool? What do you think?

[Uwe Klotz (uklotzde-deactivatedaccount)]

No, this is not necessary. Leading/trailing whitespaces in the database are unexpected, but don't cause any issues as far as I know. Moreover at this point we don't have enough context information for generating meaningful error messages.

[Daniel Schürmann (daschuer)]

At least it as confusing enough to file this bug ..
Can we print the effected name?

[nik.martin (nik-martin)]

I'd agree more debug is needed, as I was totally stuck here with no idea how to continue.

To add to the docs: This error goes away if I rebuild mixxx from source again, leading me to believe that this has something to do with dependency linking, and not an actual issue with my library (?).

In comment #3, are you saying I'm only seeing this since I run from compiled source and not a proper release? If so, then more debug output would definitely help me, because I almost always run from source, and this had me locked out good.

[nik.martin (nik-martin)]

FWIW, I did find a crate with trailing whitespace, but it has been there for several weeks, so the crash may be 100% unrelated to the debug assert which you probably already assumed. I'm guessing since I run from source when I update my OS, I need to rebuild mixxx. Is this a correct assumption?

[Be (be.ing)]

I would advise rebuilding when you update your OS, yes. IIRC when I update Fedora Mixxx will not run until I rebuild it.

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/9409