You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
This is related to issue 257 and solving that one would solve this one. I had a similar problem and the ultimate solution was not to do anything significant in the callback but just hands the work off to another thread and return. This keeps the callback code from interfering with the callback mechanism. I think that Michal, Elvin, and I decided that all callbacks need to go to the worker thread pool, though in some cases care has to be taken that whatever the callback is given remains valid.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1