For me it looks like we call a slot on of an already deleted Object.
From Qt Docu:
> All signals to and from the object are automatically disconnected, and any pending posted events for the object are removed from the event queue. However, it is often safer to use deleteLater() rather than deleting a QObject subclass directly.
Is there a "Slave" object lightening to [Master],num_samplers which is deleted together with the old skin?
We have
<attribute config_key="[Master],num_samplers">0</attribute>
in the skins
For me it looks like we call a slot on of an already deleted Object.
From Qt Docu:
> All signals to and from the object are automatically disconnected, and any pending posted events for the object are removed from the event queue. However, it is often safer to use deleteLater() rather than deleting a QObject subclass directly.
Is there a "Slave" object lightening to [Master] ,num_samplers which is deleted together with the old skin?
We have key="[Master] ,num_samplers" >0</attribute>
<attribute config_
in the skins
Or is it here: /github. com/mixxxdj/ mixxx/blob/ 7905a7e6454d77f 635b97f94758f26 9ba0e911fb/ src/widget/ wtracktableview .cpp#L110
https:/
If it turns out that this is the problem, we should switch all COs to SmartPointers with a deleteLater()