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 would be enlightening and would be my first port of call. Another approach might be some code introspection to verify that timers are cancelled and that their handlers have completed before relevant garbage collection takes place. Rather general comments I'm afraid but I thought it might be worth consideration.
Chris On 17 April 2018 at 16:36, Baptiste Robert <baptisterober...@gmail.com> wrote: > Hello, > > When I create a proton::container and use it, I have a crash when I delete > the proton object: > > void pn_proactor_free(pn_proactor_t *p) { > -> DeleteTimerQueueEx(p->timer_queue, INVALID_HANDLE_VALUE); > > I'm using proton 0.21 compiled in CXX03 mode. > > Is anyone have an idea ? > > Thank you, > > Baptiste >