New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 642474 link

Starred by 2 users
Status: WontFix
Owner:
sergeyu@chromium.org
Closed: Nov 2016
Cc:
vapier@chromium.org
█ asargent@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

native messaging host never terminates

Project Member Reported by wfh@chromium.org, Aug 30 2016 
Version: 54.0.2840.0 canary (64-bit)
OS: Windows 10.0.10586

What steps will reproduce the problem?
(1) Use Secure Shell extension/app to connect to stuff a few times
(2) Close Chrome
(3) Load task manager

What is the expected output?

No running native messaging hosts called "gnubbyagent.exe"

What do you see instead?

Lots of gnubbyagent.exe processes

Please use labels and text to provide additional information.

More context and screenshot in b/31179899

Comment 1 by lazyboy@chromium.org, Sep 2 2016

Cc: vapier@chromium.org asargent@chromium.org
+vapier (from Antony's suggestion) for gnubby question: Is this a bug in native messaging implementation or is this this a bug in gnubby code itself for not terminating properly?

Comment 2 by vapier@chromium.org, Sep 2 2016 

i'm not familiar with gnubby internals to speak to that.  i would expect that, once the request to gnubby has been fulfilled, it would clean up after itself.

Comment 3 by rdevlin....@chromium.org, Nov 11 2016

Owner: sergeyu@chromium.org
Status: Assigned (was: Untriaged)
Tentatively assigning to sergeyu@ as the nativeMessaging API owner, but I agree that there's a decent chance here that this is gnubby not fully cleaning up for some reason.

Comment 4 by sergeyu@chromium.org, Nov 11 2016

Status: WontFix (was: Assigned)
When Chrome is closed it  closes stdio pipes for NM host process. It's responsibility of the host to detect that the IO pipes have been closed and quit. So I think this is a bug that should be fixed in gnubbyagent.
►

Sign in to add a comment