For future reference, the corresponding regression preventing from starting the application has been identified and fixed in PR-6793.
Thanks for the fix. It was my mistake, I touched up a pull request with a seemingly innocent QString formatting change and there was no build error. I didn’t expect that QString::arg could fail completely at runtime like this.
The root cause of the crash was the missing return statement fixed in Slicer@cffc0f3e4
The problematic .arg()
fixed in Slicer@08fe34600 was found out while investigating and would have likely (only) returned an invalid string.
1 Like