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
>
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 /bugs.launchpad .net/bugs/ 1737619 /bugs.launchpad .net/mixxx/ +bug/1737619/ +subscriptions
> 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:/
>
> 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:/
>