std::bad_alloc after a few hours AutoDJ

Here is a mixxx.log from a crashing run:
https://bugs.launchpad.net/mixxx/+bug/1941989/+attachment/5528716/+files/mixxx.log.1
Not sure if both crashes are related.

Darren, is it possible to crash Mixxx by loading only a the few tracks that are where sheduled before and after the crash?

If you experience the crash again, are the same tracks involved?

How does the memory consumption of Mixxx changes over the time?
Is it slowly raising?

It would be also nice if you can provide a backtrace. The procedure is described here: https://github.com/mixxxdj/mixxx/wiki/Creating-Backtraces

@Darren I have just subscribed you to this bug.
Is it still an issue for you? Please have a look at my questions above.

Hi Daniel, thanks, will do!

On Thu, 30 Dec 2021, 12:35 Daniel Schürmann, <email address hidden>
wrote:

> @Darren I have just subscribed you to this bug.
> Is it still an issue for you? Please have a look at my questions above.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1944512
>
> Title:
> std::bad_alloc after a few hours AutoDJ
>
> Status in Mixxx:
> Confirmed
>
> Bug description:
> Along with skipped tracks in
> https://bugs.launchpad.net/mixxx/+bug/1941989 we have reports of
> crashes.
>
>
> https://mixxx.discourse.group/t/tracks-skipped-in-auto-dj-mode-and-eventually-mixxx-crashes/22899
>
> https://mixxx.discourse.group/t/linux-mixxx-2-3-0-crashing-on-autodj-mode/22951
>
> Eventually, when running for a few hours, Mixxx crashes with
>
> terminate called after throwing an instance of ‘std::bad_alloc’
> what(): std::bad_alloc
> Aborted (core dumped)
>
> Strange enough, running Mixxx with the loglevel “Debug” doesn’t seem
> to exhibit that behavior.
>
> As I’m using the “Auto DJ” feature quite extensively, any hint or fix
> would be highly appreciated!
>
> Some details on my environment:
>
> Linux x86_64
> Ubuntu 20.04.3
> Mixxx 2.3.0
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/1944512/+subscriptions
>
>

HI Daniel, yes, the Ubuntu Mixxx since 2.3 crashes between 12 hours and 72 hours of use on AutoDJ, which is a real issue as we have a 24/7 commitment to some radio directory services (in both U18 and U20). The track skipping however is no longer an issue since 2.3.1.

In answer to your questions:

Darren, is it possible to crash Mixxx by loading only a the few tracks that are where sheduled before and after the crash?

A: The only time it has crashed with a few tracks in the playlist is when there was a 3 hour recording in it. But it simply froze rather than completely crashed. NOTE: it has played 3 to 4 hour recordings before and since.

If you experience the crash again, are the same tracks involved?

A: No. Different tracks every time. We do have a large playlist in AutoDJ cos we broadcast 24/7 in between the live shows.

How does the memory consumption of Mixxx changes over the time?
Is it slowly raising?

A: I haven't noticed an increase in memory consumption, but will have a closer look- we're planning on restarting autodj this weekend.

By the way, I did attempt to install the backtrace feature but failed miserably. I'll have another go this coming weekend/early next week.

Thanks!

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