https://bugs.freedesktop.org/show_bug.cgi?id=56511
Stephan Bergmann <sberg...@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sberg...@redhat.com
--- Comment #2 from Stephan Bergmann <sberg...@redhat.com> ---
Are you sure that the SimpleBootstrap scenario ever worked differently? What
happens is that each SimpleBootstrap_cpp.run invokes an soffice process with an
--accept=pipe,name=unoXXX;urp; argument, where XXX is unique for each
invocation. If an soffice instance is already running in the background (which
I understand it is in your scenario), the newly invoked soffice process passes
its --accept argument to the pre-existing instances and quits. Now, the
pre-existing soffice instance dutifully opens all the different unoXXX pipes
and keeps accepting on them even after the initial client that connected on
each one has gone. At least this latter part is by design.
The overall (leaking) outcome can indeed be considered surprising, though. The
uno executable already knows a "singleaccept" mode, where it accepts only a
single connection on an acceptor and then terminates. Something similar would
probably be wanted here, like an additional "singleaccept" parameter in those
--accept arguments passed from SimpleBootstrap, so that those acceptors would
be terminated by the pre-existing soffice instance once the original client has
connected.
However, using SimpleBootstrap might not be the best solution in your scenario.
It is probably better to start the initial soffice with a well-known --accept
name and let the clients connect to that well-known name (e.g., via
com.sun.star.bridge.UnoUrlResolver).
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
