terminated by signal SIGSEGV (Address boundary error)

Bug #1737619 reported by Jeroen Mathon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Undecided
Unassigned

Bug Description

I have a library of 32.512 tracks that i wanted to analyze but apparently that is too much for the program to handle(I am suspecting a fixed array size).

Perhaps Mixxx should rely more on vectors than arrays.
This is a major issue for DJ's that need to have a big library to choose from.

Tags: memory
Revision history for this message
Jeroen Mathon (jeroenmathonmac) wrote :

Correction: +426.118 Tracks

Revision history for this message
Jeroen Mathon (jeroenmathonmac) wrote :

Size apparently does not matter.

Revision history for this message
Jeroen Mathon (jeroenmathonmac) wrote :

I am getting the following message
```
Warning [AnalyserQueue 2]: Failed to open file for analyzing: "/media/jeroen/1TB/Music/Channels/Electronic/Monstercat/Dubstep/[Dubstep] - Droptek & Tut Tut Child - Drop That Child [Monstercat Release]-IbtMWez8svU.flac"
```

Revision history for this message
Be (be.ing) wrote :

This might be a duplicate of Bug 1737537. Can you check the file size of that file mentioned in the log? Is it actually an empty file?

Revision history for this message
Jeroen Mathon (jeroenmathonmac) wrote :

After a new installation i received the following whilst running a basic scan
[code]
Warning [Main]: Unexpected number of vinyl speed preference items
Debug [Main]: in VinylGainSlotApply() with gain: 0 dB
Debug [Controller]: ControllerManager::getControllerList
Debug [Main]: LibraryScanner: Scan already in progress.
Debug [LibraryScanner 1]: LibraryScanner::slotFinishHashedScan
fish: “mixxx” terminated by signal SIGSEGV (Address boundary error)
[/code]

Revision history for this message
Jeroen Mathon (jeroenmathonmac) wrote :

I am going to reformat this drive because that might be it, since i am getting input output errors when reading from it(Which is wierd because it worked before)

Revision history for this message
Jeroen Mathon (jeroenmathonmac) wrote : Re: [Bug 1737619] Re: terminated by signal SIGSEGV (Address boundary error)

It is currently downloading the 300+GB of music from my nas to my drivd
which was prior to this formstted to exFat, noq ive formatted bit to ext4.

I will return with the test results tomorrow.

On 11 Dec 2017 10:40 pm, "Be" <email address hidden> wrote:

> This might be a duplicate of Bug 1737537. Can you check the file size of
> that file mentioned in the log? Is it actually an empty file?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1737619
>
> Title:
> terminated by signal SIGSEGV (Address boundary error)
>
> Status in Mixxx:
> New
>
> Bug description:
> I have a library of 32.512 tracks that i wanted to analyze but
> apparently that is too much for the program to handle(I am suspecting
> a fixed array size).
>
> Perhaps Mixxx should rely more on vectors than arrays.
> This is a major issue for DJ's that need to have a big library to choose
> from.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/1737619/+subscriptions
>

Revision history for this message
Uwe Klotz (uklotzde-deactivatedaccount) wrote :

The current nightly build crashes when Mixxx fails to open a file during analysis, e.g. caused by empty or corrupt files. A fix has just been merged minutes ago.

The crash while rescanning the library seems to be unrelated.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Which Version of Mixxx are you using on Which OS?

It would be great if you can produce a Backtrace with the failing disk.

https://www.mixxx.org/wiki/doku.php/creating_backtraces

Even if it was actually a hardware fault, it would be great if Mixxx gives a reasonable error message without crashing.

Revision history for this message
Jeroen Mathon (jeroenmathonmac) wrote :

I noticed that indeed it was because of a corrupt hard drive. and the issue Be mentioned.
Hereby this report can be closed as it is a duplicate, thanks for pointing me in the right direction!

Changed in mixxx:
status: New → Fix Released
milestone: none → 2.1.0
Be (be.ing)
Changed in mixxx:
status: Fix Released → Fix Committed
Changed in mixxx:
status: Fix Committed → Fix Released
Revision history for this message
Swiftb0y (swiftb0y) wrote :

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

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.