JACK latency change causes crash

Bug #191518 reported by Yorick Henning
4
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
High
Albert Santoni

Bug Description

When you change the latency with JACK selected as API, you get a fatal assert:

First time:
ASSERT: "m_pControlObject" in file src/controlobjectthread.cpp, line 32

Fourth time:
Debug: Opened PortAudio stream successfully... starting
Debug: PortAudio: Started stream successfully
Fatal: ASSERT: "m_pControlObject" in file src/controlobjectthread.cpp, line 32
Aborted (core dumped)

Getting the program back into this condition, I couldn't do though. Yet another race probably... The wonders of threaded programming. :)

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

Yorick, does this happen in beta2 and/or SVN still?

Thanks! (I can't remember if I fixed this or not...)

Changed in mixxx:
importance: Undecided → High
status: New → Triaged
Revision history for this message
Yorick Henning (p-yorick) wrote : Re: [Bug 191518] Re: JACK latency change causes crash

This is still happening. Sp'ifically, it now happens on startup once
you've configured to JACK and closed down once - terminating JACK and
starting up again fixes it though (Mixxx realises there's no jackd and
reverts to ALSA I suppose).

I notice that the latency slider is now locked at 16ms for JACK
though. Is it actually 16ms or 0ms? But given the latency slider is
locked, I can't really tell if changing it on the fly causes a crash,
can I? ;)

~Y

On Sun, Mar 2, 2008 at 6:05 AM, Albert Santoni <email address hidden> wrote:
> Yorick, does this happen in beta2 and/or SVN still?
>
> Thanks! (I can't remember if I fixed this or not...)
>
> ** Changed in: mixxx
> Importance: Undecided => High
> Status: New => Triaged
>
>
> --
> JACK latency change causes crash
> https://bugs.launchpad.net/bugs/191518
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Mixxx: Triaged
>
>
>
> Bug description:
> When you change the latency with JACK selected as API, you get a fatal assert:
>
> First time:
> ASSERT: "m_pControlObject" in file src/controlobjectthread.cpp, line 32
>
> Fourth time:
> Debug: Opened PortAudio stream successfully... starting
> Debug: PortAudio: Started stream successfully
> Fatal: ASSERT: "m_pControlObject" in file src/controlobjectthread.cpp, line 32
> Aborted (core dumped)
>
> Getting the program back into this condition, I couldn't do though. Yet another race probably... The wonders of threaded programming. :)
>

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

Ok, thanks for the update Yorick, I'll have to play around and try to reproduce this on my system....

Albert Santoni (gamegod)
Changed in mixxx:
assignee: nobody → gamegod
status: Triaged → Fix Committed
Revision history for this message
seamus1089 (s-holden1) wrote :

This still occurs in beta3 btw.

Cheers
Seamus

Revision history for this message
ironstorm (ironstorm-gmail) wrote :

This was marked as fixed.... But was it?

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

Yes, latency is no longer changeable with JACK as an API, because it's
determined by the JACK daemon anyways.

On Mon, Nov 17, 2008 at 3:41 PM, ironstorm <email address hidden> wrote:
> This was marked as fixed.... But was it?
>
> --
> JACK latency change causes crash
> https://bugs.launchpad.net/bugs/191518
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
>

Revision history for this message
ironstorm (ironstorm-gmail) wrote :

fair enough, closing.

Changed in mixxx:
status: Fix Committed → Fix Released
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/issue/4916

lock status: Metadata changes locked and limited to project staff
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/4916

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.