when using Auto DJ on windows 7 64 bit it will unexpectedly shut off and have to be opened again.

[LetDiane Mary Spina]

Windows 7
quad core AMD Radeon1.60 GHz
beats Audio Hp Pavilion

dvd-6c35dx entertainment pc

load tracks into auto Dj enable it turn up sound and then crashes at no particular time.

[jus (jus)]

I can confirm this using the 32bit Mixxx 1.10.1beta1 version on WIn7.
Minidump available by request.

[jus (jus)]

Oops, should read "...using the 32bit Mixxx 1.11.0beta1 ..." in post #1.

[Mark Booth (markybooth)]

Is your machine 32bit? I was having a similar problem but then realised there's a 64bit version that works fine on my 64bit machine.

[RJ Skerry-Ryan (rryan)]

Jus -- is this still reproducible?

[Raf Van De Meirssche (rafvdm)]

I see this old post.
I experienced the problem yesterday with the 1.12-r4518 beta-build too..

Can't remember which PC, as I was installing the beta-build on both PC's thru a KVM-switch.
My laptop runs 64-bit Windows 7 Home Premium.
My desktop runs 32-bit Windows 7 Ultimate.

What did I do?
- Uninstalled the Mixxx 1.11
- Uninstalled Mixxx 1.12 alpha-build
- Installed Mixxx 1.12 beta-build
- Started Mixxx in Dutch (though I guess the language has no influence at all)
- Mixxx complained my audio hardware settings were not correct (which was correct as my ESI was not connected) and automatically presented the preference panel
- I changed the audio hardware settings in it
- Also changed some other settings but don't remember which
- After OK, Mixxx was automatically and correctly entered
- I immediately went to the AutoDJ list, cleared all pending tracks (Ctrl+A, right click, remove) and added new tracks from my Quick Links
- I guess (but am not sure!) a pressed the Shuffle button then
- Then pressed the Enable AutoDJ button
- Mixxx just plainly ended with no messages at all :-(

I had the problem on 1 PC only.
On the other PC I either was not confronted with the audio hardware issue, or I continued and did not pass through the automatically presented settings panel.

I guess with the beta there is always a log?
If it is not automatically cleared at start, I suppose it could help.
What information do I look for to see which of both logs you need?

Anyway ... Up to now I see this as a minor issue, guess it happens in very specific circumstances only.
I will probably try to reproduce the case, but don't know when this will be.

[Daniel Schürmann (daschuer)]

Yes we have logs. You van found them in %LOCALAPPDATA%\Mixxx
Please attach the one of the crash here. Thank you.
Please do not start Mixxx before saving the logs. So they are not overwritten.

If you are able to reproduce the crash a back-trace will be helpful as well
http://www.mixxx.org/wiki/doku.php/creating_backtraces

[Owen Williams (ywwg)]

Also please try a newer build of Mixxx and specify if you're building from the master branch or 1.12 branch.

And Daniel, we save the logs from the previous 10 launches of Mixxx under mixxx.log.1, mixxx.log.2, etc. So restarting mixxx a couple times will not overwrite the data :)

[Raf Van De Meirssche (rafvdm)]

Sorry, can't build
Just using the ready-to-go exe :-)

Log files and cfg from the 64-bit laptop attached
Remember, I'm not sure if it happened on this PC
I did restart Mixxx afterwards a few times, I hope that was less than 10 :-)

I'll upload the 32-bit version as soon as possible

[Raf Van De Meirssche (rafvdm)]

For the backtrace:
Do I understand well that this is to be done only if I know how to reproduce the bug?
And do I understand well that I need some specific debug version of Mixxx, or will the regular beta-exe do?
If not the regular beta, where can I find this debug version?
Also the instructions are not clear from "6. Continue with the instructions below for all platforms" in the Windows part.
Please clarify, so I am prepared.

[Raf Van De Meirssche (rafvdm)]

... the 32-bit log
Same comments apply

One more information that might help:
I'm pretty convinced that I encountered this problem immediately after installing 1.12
So focus on the first 1.12 log

[Daniel Schürmann (daschuer)]

Win7ultimate64bit:
all files are terminated with:
Debug [Main]: Mixxx shutdown complete with code 0

Win7homepremium32bit:
mixxxx.log.6 /5/4/3/2/0

All logs a truncated but not the fist (7)

Unfortunately I cannot recognize a schema.

We have in 5 and 6:
  Debug [Main]: SchemaManager::upgradeToSchemaVersion Don't know how to get to 18 from 17
This issue seams to be solved in run 4:
  Debug [Main]: Applying version 18 : "Add keys column to library table."

A Suspicious path in 4:
  Debug [LibraryScanner 1]: Found moved track! "Francis Lai - Made In U.S.A.\B0.mp3
Please report the full path. What is the symbol before .mp3?
The log terminates with:
 Debug [LibraryScanner 1]: Found moved track! "Gloria Estefan - Words Get In The Way.mp3"

3: Crashes with:
 Debug [AnalyserQueue 1]: Analyzing "Can You Feel It" "M:/Categorie 1/80/80.Disco.Early80s/Jacksons - Can You Feel It.mp3"

2: Crashes with:
Debug [AnalyserQueue 1]: Analyzing "Hit The Road Jack" "//RNINWD1/2_Muziek/_Raf [KopieFG]/_FunGun/_Muziek/Categorie 1/60/60.Jive/Ray Charles - Hit The Road Jack.mp3"

1/0: Crashes with:
Debug [Main]: No output devices opened, no clock reference device set

We may investigate all these crashes individual, but it is uncommon, that this all happens in consecutive runs.
So I assume there is something els going on. Probably a memory leak or such issue.
On the other hands the two most recent runs crashes similar.

Next steps: Please install our latest release builds and check if the crash still occurs.
http://downloads.mixxx.org/builds/1.12/release/mixxx-1.12.0-beta1-1.12-git5424-release-x86.exe
There are no debug symbols in release and debug builds :-( (we build both with /Zi)
If yes watch the memory consumption during startup it should stop below 500 MB.
Then install Mixxx within GDB.
I have just improved the instructions: "Continue with step 2. in the section below"
I hope the backtrack is significant enough

Thank you for your help.

[Raf Van De Meirssche (rafvdm)]

I see that my M: drive letter isn't connected anymore.
To say at least that I havn't used Mixxx that much on my home PC lately. :-(
And normally I use it as another user too, but there also the network drive isn't connected anymore.

I think this explains a number of these problems.
But of course the crashes should still be solved by you developpers.
Again very specific circumstances, so for me not urgent at all.

I do remember noticing that the start up library scan took very little time on 1 of my machines.
I guess it was on this PC.
Never realized there could be a problem with it.
So perhaps it would be nice to get a message until there is a good solution.
Only if this would not take too long to develop, I understand that there are more issues and more urgent ones to solve.
So NO for an intermediate solution would still be OK, no problem at all.

The symbol in ""Francis Lai - Made In U.S.A.\B0.mp3" is a degree sign on my Belgian Keyboard that never ever has posed any problem.
I don't know how to see the binary value easily.
If you need it, tell me how to find it.

By now, I intend to reconnect the network drive and clean the database on this PC soon.
I will then try out this backtrack thing, so we can see if any abends remain.
If anyone wants me to do some more testing with this "bad" set up first, he/she must let me know promptly.

I have the feeling that we've gone off the right track a bit because of this missing drive letter issue.
Of course, I will still try to reproduce the initial problem as I experienced it.
But I will still not be able to try and reproduce this right a way.

Thank you for all your efforts.

[Vladimír Dudr (vlada-dudr)]

This looks like same problem I was reporting here:
https://bugs.launchpad.net/mixxx/+bug/1467293

[RJ Skerry-Ryan (rryan)]

I believe this was fixed -- please reopen if you hit this on Mixxx 2.0!

[Swiftb0y (swiftb0y)]

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