Is one of your completion handlers throwing an exception? On Mon, 7 Apr 2025 at 18:04, João Fernando Silva via Boost-users < boost-users@lists.boost.org> wrote:
> Hi Vinnie, > > Unfortunately we are unable to do so. We have only seen this happen with a > specific application that interacts with our code (which is proprietary) > and could not replicate it elsewhere. > > You can take a look at our code here https://github.com/COVESA/vsomeip. > The relevant lines in this case are these > > > https://github.com/COVESA/vsomeip/blob/master/implementation/runtime/src/application_impl.cpp#L54-L56 > > https://github.com/COVESA/vsomeip/blob/master/implementation/runtime/src/application_impl.cpp#L466-L474 > > https://github.com/COVESA/vsomeip/blob/master/implementation/runtime/src/application_impl.cpp#L504-L514 > > Thanks > ------------------------------ > *From:* Vinnie Falco <vinnie.fa...@gmail.com> > *Sent:* Monday, April 7, 2025 3:51 PM > *To:* boost-users@lists.boost.org <boost-users@lists.boost.org> > *Cc:* João Fernando Silva < > joao.fernando.si...@partner.criticaltechworks.com> > *Subject:* Re: [Boost-users] Issues with boost executor_work_guard > > *Notice:* This e-mail has originated from an external email service, so > do not click on any links, nor open any attachments unless you know who the > sender is and are sure the content is secure. > > > > On Mon, Apr 7, 2025 at 7:07 AM João Fernando Silva via Boost-users < > boost-users@lists.boost.org> wrote: > > ...despite the work_guard still being valid, we see that the threads exit > because boost::asio::detail::scheduler::outstanding_work reaches 0. > > > If you could create a small, self-contained program which demonstrates > this behavior it would be very helpful for diagnosing the problem. > > Thanks > > The information in this communication may contain confidential or legally > privileged information. It is intended solely for the use of the individual > or entity it addresses and others authorized to receive it. If you are not > an intended recipient, you are hereby notified that any disclosure, > copying, distribution or action in reliance on the contents of this > information is strictly prohibited and may be unlawful. If you have > received this communication by error, please notify us immediately by > responding to this e-mail and then delete it from your system. Critical > TechWorks is not liable for the proper and complete transmission of the > information in this communication nor for any delay in its receipt > > *This e-mail is environmentally friendly, just like Critical TechWorks, > which lives in a paper-free atmosphere. Therefore, please consider the > environment before printing it! * > _______________________________________________ > Boost-users mailing list > Boost-users@lists.boost.org > https://lists.boost.org/mailman/listinfo.cgi/boost-users >
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-users
