Native Messaging host doesn't run under Windows
Reported by
aleksand...@stickypassword.com,
Mar 2 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: 1. Install Sticky Password application 2. Install Sticky Password extension into Chrome What is the expected behavior? Everything works fine - pages auto-filled, extension icon is color and shows the Sticky Password GUI while clicking on it. What went wrong? Sometimes for some users the Native Messaging Host for unknown reason doesn't run at all. It is successfully registered using registry key, the manifest file is correct and specify the existing Native Messaging Host application path. We've tried to read the "chrome_debug.log" file while launching the Chrome with "--enable-logging --v=1" params - nothing relative to Native Messaging at all in the log and even no errors has been there! If I'm not wrong even in the extension console nothing written about errors. When user reinstall the Chrome - everything start working as expected. How can we found what causes this issue? Did this work before? N/A Does this work in other browsers? N/A Chrome version: 56.0.2924.87 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0
,
Mar 2 2017
Well, how can graphics in that trace screen help me to found the issue?
,
Mar 2 2017
You can zoom the chart to see function names, events, data. It's pretty awkward to use, though.
,
Mar 2 2017
May be I can zoom it, but not the user. Not all users allow the remote session, so we need some simple solution which allows to remotely find the issue.
,
Mar 2 2017
And if I'm not wrong this tool is used for searching the performance problems as it is written in the document. I can't see there errors.
,
Mar 7 2017
@aleksandr.guk-- Could you please provide us the sample extension and screencast of the issue , that would help us in reproducing the issue better. Thanks!
,
Mar 7 2017
This issue can't be reproduced on our side. Only couple of users had this issue (3 or 4). Is there any extended logging in Chrome which help us to find the issue?
,
Mar 7 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 14 2017
,
Oct 16 2017
As per comment# 7, marking the issue as Won't Fix. Please feel free to raise a new bug if the issue is again seen. Thank You. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by woxxom@gmail.com
, Mar 2 2017