Critical [Engine]: DEBUG ASSERT: "pState != nullptr" in EffectProcessorImpl<FilterGroupState>

[jus]

macOS 10.13.3 mixxx 2.1.0-beta1 (build 2.1 r6543)

./mixxx --developer --resourcePath res

On launch, following is printed to the log:

``
Critical [Engine]: DEBUG ASSERT: "pState != nullptr" in function virtual void EffectProcessorImpl<FilterGroupState>::process(const ChannelHandle &, const ChannelHandle &, const CSAMPLE *, CSAMPLE *, const mixxx::EngineParameters &, const EffectEnableState, const GroupFeatureState &) [EffectSpecificState = FilterGroupState] at src/effects/effectprocessor.h:154
Critical [Engine]: DEBUG ASSERT: "pState != nullptr" in function virtual void EffectProcessorImpl<FilterGroupState>::process(const ChannelHandle &, const ChannelHandle &, const CSAMPLE *, CSAMPLE *, const mixxx::EngineParameters &, const EffectEnableState, const GroupFeatureState &) [EffectSpecificState = FilterGroupState] at src/effects/effectprocessor.h:154
``

Not found any implications during performance, but use effects sparely.

[Be (be.ing)]

Do you recall what you were doing when this happened? Is it reproducible? Did you have the Filter effect loaded in the regular effects or only as a QuickEffect? If you were changing the old [EffectRack1_EffectUnitX], enabled Control somehow, this may be a duplicate of 1748061.

[jus (jus)]

Id say it is a duplicate of lp:1748061 . But it did not crash on me, just the warning. My guess i that it has something to do with using the the 2.0 and 2.1-dev, sharing the same *.cfg.

Deleting the mixxx.cfg makes the message go away when launching v2.1-dev. I tried different combination of 2.0 / 2.1-dev settings ( changing default skins, with- and without effects) to no avail. Could not reproduce.

I did not have any quickeffects loaded other then the default ( Filter in mixer section)

[Be (be.ing)]

Were you using [EffectRack1_EffectUnitX], enabled?

[jus (jus)]

A screenshoot of my config, the last time the messages appeared on launch in the log. Afterwards, i went to delete the mixxx.cfg, and the message went poof.

[Daniel Schürmann (daschuer)]

This could also be a duplicate of recently fixed
https://bugs.launchpad.net/mixxx/+bug/1758189

[Be (be.ing)]

I don't think #1758189 has to do with this.

[Be (be.ing)]

jus, have you been able to reproduce this since deleting your config file?

[jus (jus)]

Unfortunately not.

[jus (jus)]

Update:
Using the following files, i was able to reproduce it. The message is printed to the log on launch.

[Be (be.ing)]

I tried starting Mixxx with those mixxx.cfg and effects.xml files and did not see the debug assertion in the log.

[RJ Skerry-Ryan (rryan)]

Has this recurred? Should we assume this got fixed in the various changes leading up to the 2.1.x release?

[Be (be.ing)]

If I remember correctly, this was another symptom of Bug #1748061 that was fixed by https://github.com/mixxxdj/mixxx/pull/1602

[Be (be.ing)]

Hm, Launchpad won't let me retroactively assign this to the 2.1.0 milestone :/

[RJ Skerry-Ryan (rryan)]

That's our own choice to mark milestones "inactive". I just marked 2.0.0 and 2.1.0 active again so we can target bugs to them because it prevents us from correcting history like in this case.

[Swiftb0y (swiftb0y)]

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