Random crash on Win 7

Bug #657172 reported by Josh Vickerson
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Critical
Albert Santoni
1.8
Fix Released
Critical
Albert Santoni

Bug Description

I've recently begun using Mixxx 1.8.0 (final) on a Windows 7 desktop. It's a completely fresh install (deleted anything related to Mixxx before installing, cleaned registry, etc.) and I'm only able to use it for a few minutes before it closes. I don't receive any error message or even the Windows dialog saying an application quit unexpectedly or has stopped responding or anything. It just closes. I'm not entirely sure how you would go about reproducing the problem unless this is pretty common...

PC:
Windows 7 Home Premium (32-bit) [all recent updates installed]
2.4GHz Athlon 64 (AMD Athlon(tm) 64 X2 Dual Core Processor 4400+)
GeForce 6150SE nForce 430 video card (128MB, using most recent driver)
Realtek High Definition Audio sound card

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Hi Josh,

Thanks for taking the time to file a bug. Could you please tell me what settings you have in your in your Audio preferences, specifically the Audio API, the Master/Headphone devices you chose, your latency, and your sample rate?

Are you using any MIDI controller or Vinyl Control?

Thanks,
RJ Ryan

Revision history for this message
Josh Vickerson (jpv41193) wrote :

Nope, no MIDI or Vinyl Control, just some real simple mixing (I'm just getting into DJing)

My latency is set to 42ms, my master device is just "primary sound driver", no headphones, sample rate is 48,000, audio API is Windows Direct Sound.

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Ok, I've got a Windows 7 64-bit VM. I'm trying to reproduce the issue with your settings. Nothing yet, but I'll let you know if I get anywhere.

In the mean-time, could you please try changing your settings to see if you can still trigger the problem with different settings?

1) Please try it with your sample rate at 44.1kHz
2) Please try using the WASAPI Sound API
3) Please try using the ASIO API. You may need to install ASIO4ALL from http://asio4all.com

Also, are you a new Mixxx user, or have you used previous versions? If so, did you experience the same crashes before?

After you've tried out 1-3, if you're still up for it, could you please install Mixxx 1.7.2 from here:
http://moo.glines.org/mixxx/mixxx-1.7.2/mixxx-1.7.2-win32.exe
and let me know if the crash occurs with Mixxx 1.7.2?

That would be really useful for helping us track down the issue.

Thanks!
RJ Ryan

tags: added: segfault
Revision history for this message
Josh Vickerson (jpv41193) wrote :

I tried increasing the latency to 85ms with my original settings and had the same result.
I've tried 44.1kHz (46s latency) and got the same result.

I can't use WASAPI because the only output I can select then is the digital out (which I have no speakers for).

I'm not brand new to Mixxx but I'm not terribly experienced. I used 1.7.2 on this same computer for a few weeks before 1.8.0 was released and had no issues (and was able to set my latency to 21ms without problems). All in all I've noticed a slight decrease in performance from this release. I tried using 1.7.2 again and started looking for more differences. In 1.8.0 there is a slight skip (I mean like a fraction of a second) whenever a song is playing and I load another into the other track. If I skip to a point in a song by clicking the wave-form while it's playing it skips a little bit (both of these happened with 85ms latency). I had neither of these issues with 1.7.2.

I've downloaded the ASIO API but haven't gotten to trying it yet. Thought I'd give you an update in the meantime.

Revision history for this message
Albert Santoni (gamegod) wrote : Re: [Bug 657172] Re: Random crash on Win 7

Hi Josh,

Regarding the crash, do you typically have vinyl emulation or pitch
independent time stretch selected in the preferences?

Can you please see if you can reproduce the crash if you switch to the other
option?

Thanks,
Albert
On 2010-10-09 9:05 PM, "Josh Vickerson" <email address hidden> wrote:
> I tried increasing the latency to 85ms with my original settings and had
the same result.
> I've tried 44.1kHz (46s latency) and got the same result.
>
> I can't use WASAPI because the only output I can select then is the
> digital out (which I have no speakers for).
>
> I'm not brand new to Mixxx but I'm not terribly experienced. I used
> 1.7.2 on this same computer for a few weeks before 1.8.0 was released
> and had no issues (and was able to set my latency to 21ms without
> problems). All in all I've noticed a slight decrease in performance from
> this release. I tried using 1.7.2 again and started looking for more
> differences. In 1.8.0 there is a slight skip (I mean like a fraction of
> a second) whenever a song is playing and I load another into the other
> track. If I skip to a point in a song by clicking the wave-form while
> it's playing it skips a little bit (both of these happened with 85ms
> latency). I had neither of these issues with 1.7.2.
>
> I've downloaded the ASIO API but haven't gotten to trying it yet.
> Thought I'd give you an update in the meantime.
>
> --
> Random crash on Win 7
> https://bugs.launchpad.net/bugs/657172
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.

Revision history for this message
Josh Vickerson (jpv41193) wrote :

So using my original settings I described and changing from vinyl emulation to independent time stretch it doesn't seem to crash. Before I would use it for about 20-30 minutes and then it would just close. I was able to use it as I normally would for 45 minutes without it crashing by selecting independent time stretch.

Revision history for this message
Josh Vickerson (jpv41193) wrote :

To be clear, I only stopped using it after 45 minutes, it never crashed.

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Hmm, ok thanks. Could you post your mixxx.log file? You should be able to find this in C:\Program Files\Mixxx\mixxx.log. I'm not totally familiar with our Windows installer so it might be slightly different.

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

(btw I meant post your mixxx.log right after it crashes)

Revision history for this message
Albert Santoni (gamegod) wrote :

I found a bug in EBSL using Valgrind that is likely the cause of this crash. I've added a workaround that clamps prev_sample in enginebufferscale.cpp to prevent the out-of-bounds access, since we're probably going to be doing something drastic with this code in the near future.

The fix is committed in the 1.8 branch, r2653.

Josh: Thanks for reporting this bug. A crash like this is a critical bug and fortunately you reported it so we were able to fix it sooner rather than later. We will be releasing 1.8.1 as soon as we can to get the fix out.

Revision history for this message
Josh Vickerson (jpv41193) wrote :

Excellent! I'm looking forward to the release. And now I'm curious about the "drastic" code changes and what it means for Mixxx... but don't ruin the surprise :)

RJ Skerry-Ryan (rryan)
Changed in mixxx:
status: New → Fix Released
importance: Undecided → Critical
assignee: nobody → Albert Santoni (gamegod)
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/5554

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.