I do not use any kind of timer on my side, but maybe it's a similar
internal proton issue as this one :
https://issues.apache.org/jira/browse/DISPATCH-945
2018-04-18 2:21 GMT+02:00 Chris Richardson :
> A couple of suggestions spring to mind - I've experienced problems with
>
A couple of suggestions spring to mind - I've experienced problems with
timers in other libraries where a timer fires after (or indeed during) its
callback or associated data has been deleted, resulting in a segfault.
Could this be relevant? Probably capturing a core dump and inspecting with
gdb