Mixxx Crash with tracks on a bad drive

[Jay Harvey]

I was so Happy to Download my new copy of Mixxx 2.0

Installed it over Mixxx 1.11 and all went well... Once it opened up on my Screen, I immediately load in my music directory... :( I had 46 not analyzed yet, so I ran them through the analyzer and by the 28 song Mixxx 2.0 crashed.

I am Running on Windows 10 Home Edition
CPU Type Intel Pentium III Xeon, 2600 MHz
Video Adapter Intel(R) G33/G31 Express Chipset Family (256 MB)
3 GB of Memory

I going to try a fresh install today and see what happens

In the meantime suggestions are welcome.

[Sébastien BLAISOT (sblaisot)]

Hi Jay,

Can you attach the log file from the crash session ?
It's usually located in C:\users\<login>\AppData\Local\Mixxx and is named mixxx.log (or mixxx.log.X if you have run X sessions after that crash)

Thanks.

sb

[Sébastien BLAISOT (sblaisot)]

Also, can you tell us if you use 32 ou 64 bits windows and 32 or 64 bits Mixxx ?

[Jay Harvey (jharveysxm)]

32 bit Windows and 32 bit Mixxx

On Wed, Dec 30, 2015 at 9:28 AM, Sébastien BLAISOT <email address hidden>
wrote:

> Also, can you tell us if you use 32 ou 64 bits windows and 32 or 64 bits
> Mixxx ?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1530107
>
> Title:
> Mixxx Crash while analyzing Tracks
>
> Status in Mixxx:
> New
>
> Bug description:
> I was so Happy to Download my new copy of Mixxx 2.0
>
> Installed it over Mixxx 1.11 and all went well... Once it opened up on
> my Screen, I immediately load in my music directory... :( I had 46
> not analyzed yet, so I ran them through the analyzer and by the 28
> song Mixxx 2.0 crashed.
>
> I am Running on Windows 10 Home Edition
> CPU Type Intel Pentium III Xeon, 2600 MHz
> Video Adapter Intel(R) G33/G31 Express Chipset Family (256 MB)
> 3 GB of Memory
>
> I going to try a fresh install today and see what happens
>
> In the meantime suggestions are welcome.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/1530107/+subscriptions
>

[Jay Harvey (jharveysxm)]

bug tracer

On Wed, Dec 30, 2015 at 11:46 AM, Sébastien BLAISOT <email address hidden>
wrote:

> *** This bug is a duplicate of bug 1530141 ***
> https://bugs.launchpad.net/bugs/1530141
>
> ** This bug has been marked a duplicate of bug 1530141
> Crash on analyzing tracks
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1530107
>
> Title:
> Mixxx Crash while analyzing Tracks
>
> Status in Mixxx:
> New
>
> Bug description:
> I was so Happy to Download my new copy of Mixxx 2.0
>
> Installed it over Mixxx 1.11 and all went well... Once it opened up on
> my Screen, I immediately load in my music directory... :( I had 46
> not analyzed yet, so I ran them through the analyzer and by the 28
> song Mixxx 2.0 crashed.
>
> I am Running on Windows 10 Home Edition
> CPU Type Intel Pentium III Xeon, 2600 MHz
> Video Adapter Intel(R) G33/G31 Express Chipset Family (256 MB)
> 3 GB of Memory
>
> I going to try a fresh install today and see what happens
>
> In the meantime suggestions are welcome.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/1530107/+subscriptions
>

[Jay Harvey (jharveysxm)]

The Problem seem to be a bad drive.... the drive crashed and load all the music on a new drive and it worked well

But Mixxx got to work on this, the Mixxx should not crash, no other DJ software the crash happen with.

[Daniel Schürmann (daschuer)]

Yes, that's true Mixxx should not crash for any reason.

Unfortunately the backtrace is incomplete.
It seams also that the backtrace part is unreliable because the crash was too bad and destroys the call stack as well.

Are yo able to produce an new backtrace. I am especially interested in the tail of the Mixxx console output and the backtrace of the crashing thead. This is printed in gdb by typing "bt"

[Launchpad Janitor (janitor)]

[Expired for Mixxx because there has been no activity for 60 days.]

[Swiftb0y (swiftb0y)]

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