Attached is my log from the most recent crash. This has happened several times during sets, even after restarting, and as one might guess, it suuuuucks. It has never happened when using the DidJiX liveCD, which I have for several long sets. That distro has other problems though, namely playing deck's track skipping on cue deck's track load, maybe due to it using a Mixxx version vulnerable to this bug: "http://<email address hidden>/msg02684.html", so I would prefer not to use it.
I'm running XP Pro SP3, 1.60ghz, 753mb, onboard SigmaTel audio running out to the speakers with a crappy $2.75 Hong Kong C-Media USB sound card to the headphones (the sound to the headphones skips but I don't report that as a bug because I figure it has to do with my weak hardware rather than Mixxx). However, when I had the crashes during sets, though I was using the same C-Media external USB sound card for headphones, my hardware was 1.4ghz single core with 2gb of memory, but also running XP Pro, though SP2. I think the audio out was just onboard Realtek.
My Mixxx music library points to my 16gb USB flash drive, and the crashes happen not immediately, they happen as much as an hour and as little as a half an hour into a set. This of course makes it difficult to test for repeatability, since I don't always have a half an hour or more to devote to loading track after track into Mixxx to see if it crashes :/
I don't recall this happening with the 1.9 and earlier releases, but, by coincidence, I have been doing more sets since 1.10 so I'm not entirely sure the version change is relevant. It could just be that I've never done as many and as long of sets before 1.10.
My psychic powers tell me that the USB drive has something to do with it. I can't justify that, sorry, psychic power is mysterious. I'll run some sets from the disk instead to see if the same happens, but since some sets pass just fine anyway, I'm not sure that can help with being conclusive.
I'm hoping to have some clues before my next set in a couple of weeks :'((
UPDATE 08/01:
Last night I did a set with the 1.11.0 beta2 pre 3314 build. I had done a 3 hour test set before the actual set, using the same hardware I would be using for the set, to determine if it would crash, and it did not. However, later that evening during the actual set Mixxx did indeed crash about 3 hours into it. I was able to hurriedly restart and only had about ten seconds of dead air, but in the rush could not recover the log file. Mixxx did not crash for the remaining hour or so of the set.
The other problem I had consistently during both the practice and the real set was that when loading tracks into the cue deck the playing deck would hang for a minute - not keep playing and lose sound, but actually stop for about half a second before resuming. This was happening while the cue deck waveforms were being generated on the screen; I was using the filtered - software renderer at a default zoom of 16.7% and a framerate of 30, which had proven to be the most stable settings thus far - all the other zooms or renderers hung the playing deck more frequently. I also noticed that files with bitrates below 192, which is what almost all of my files are, seemed to cause the hang more. Also, all of my files had been analyzed by Mixxx's new 1.11 bpm scanning beforehand because I'd heard the scan also pregenerates the waveforms, which I figured would help. Apparently not :/
As a punctuation, in the event that this all is a cpu spec issue, I'd like to make a request that lower spec computers like mine be accommodated in the development. I don't think 1.4ghz single core is absurdly weak even by today's standards, it seems reasonable to expect an application like Mixxx to play well with it. Turning off waveforms sucks, not having beatgrids sucks. Anyway, turning off waveforms doesn't even help completely since skins have mini waveforms for the video card to deal with regardless.
Sorry to clutter up the page with my edits, I didn't realize that would happen and I'll do them offline in the future.