When setting up SignalTransition { onTriggered: /.../ }{}, it can happen that this causes a segfault when creating the component. See the attached minimal example and the two stack traces.
| For Gerrit Dashboard: QTBUG-110286 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 456290,3 | StateMachine: Don't crash if no signal is passed to SignalTransition | dev | qt/qtscxml | Status: MERGED | +2 | 0 |
| 456317,2 | StateMachine: Don't crash if no signal is passed to SignalTransition | 6.5 | qt/qtscxml | Status: MERGED | +2 | 0 |
| 456358,2 | StateMachine: Don't crash if no signal is passed to SignalTransition | 6.4 | qt/qtscxml | Status: MERGED | +2 | 0 |
| 456364,2 | StateMachine: Don't crash if no signal is passed to SignalTransition | tqtc/lts-6.2 | qt/tqtc-qtscxml | Status: MERGED | +2 | 0 |
| 456365,1 | StateMachine: Don't crash if no signal is passed to SignalTransition | tqtc/lts-5.15 | qt/tqtc-qtscxml | Status: ABANDONED | 0 | 0 |
| 456444,2 | StateMachine: Don't crash if no signal is passed to SignalTransition | tqtc/lts-5.15 | qt/tqtc-qtdeclarative | Status: MERGED | +2 | 0 |