dbus-launch leaks a process #268
Comments
|
I think it does. I believe @fawkesley and @jessevdk have worked in this area of the code before. Do either of you have an opinion here? |
|
Can we move this forward? I can open a PR if there is an agreement on the way to fix it. |
|
If you have a PR then I'll review it. |
giuseppe
added a commit
to giuseppe/dbus
that referenced
this issue
Oct 18, 2021
SessionBusPrivate automatically launches dbus-launch when the other detection mechanisms fail. SessionBusPrivateNoAutoStartup returns an error without executing a new process, so that it is not leaked. Closes: godbus#268 Signed-off-by: Giuseppe Scrivano <[email protected]>
opened a PR here: #273 |
jsouthworth
pushed a commit
that referenced
this issue
Oct 26, 2021
SessionBusPrivate automatically launches dbus-launch when the other detection mechanisms fail. SessionBusPrivateNoAutoStartup returns an error without executing a new process, so that it is not leaked. Closes: #268 Signed-off-by: Giuseppe Scrivano <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
the function
getSessionBusAddress()callsgetSessionBusPlatformAddress()if there is no dbus session already active.getSessionBusPlatformAddress()in turn runsdbus-launchwhich leaks the process.Issues reported here: containers/podman#9727
Would it make sense to have a way to disable the
getSessionBusPlatformAddress()fallback and avoid runningdbus-launch?The text was updated successfully, but these errors were encountered: