New issue
Advanced search Search tips

Issue 921630 link

Starred by 1 user
Status: Unconfirmed
Owner: ----
Cc:
viswa.karala@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome Extension, Message Passing - Long Life Connection

Reported by sharonab...@gmail.com, Jan 14 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.53 Safari/537.36

Steps to reproduce the problem:
We publish an extension on the Chrome store (unlisted). 
The extension uses Native Messaging and connects to native code on the host.
We use chrome.runtime.onMessage.addListener(function callback) to pass messages. 
A few days ago the callback function stopped returning the MessageSender parameter from the native code. The MessageSender parameters returns empty.

This causes a loss of communication between the extension and the native code.
The extension stopped working and we started to get error messaged that the port is disconnected.

What is the expected behavior?

The connection between the extension and the host should long live.

What went wrong?
The MessageSender should contain the Sender.Name = port ID, however it is empty.

Did this work before? Yes Chrome 71

Does this work in other browsers? Yes

Chrome version: 72.0.3626.53  Channel: beta
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

Please contact me for details regarding the extension and URLs for reproduction.

Comment 1 by phanindra.mandapaka@chromium.org, Jan 14

Labels: Needs-Triage-M72 Needs-Bisect

Comment 2 by dtapu...@chromium.org, Jan 14

Components: Platform>Extensions

Comment 3 by viswa.karala@chromium.org, Jan 16

Cc: viswa.karala@chromium.org
Labels: Triaged-ET Needs-Feedback
Thanks for filing the issue!

@Reporter: Could you please provide sample Extension File/URL that reproduces the issue which help in further triaging the issue in better way.

Thanks!

Comment 4 by phistuck@chromium.org, Jan 16 (6 days ago)

Labels: -Hotlist-Interop

Comment 5 by sharonab...@gmail.com, Jan 17 (5 days ago) 

Thanks viswa.karala, I sent you an email with the URL to reproduce.
Please contact me for further information.
Sharona.
Project Member

Comment 6 by sheriffbot@chromium.org, Jan 17 (5 days ago)

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 7 by viswa.karala@chromium.org, Jan 18 (4 days ago)

Labels: Needs-Feedback
@Reporter: Updated the behavior and shared the screencast of the issue through email with the URL provided, hence adding Needs-Feedback label to it.

Thanks!

Comment 8 by sharonab...@gmail.com, Jan 20 (2 days ago) 

Thanks viswa.karala, I responded to your message.
Project Member

Comment 9 by sheriffbot@chromium.org, Jan 20 (2 days ago)

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 10 by viswa.karala@chromium.org, Yesterday (45 hours ago)

Labels: Needs-Feedback
@Reporter: Updated the behavior and shared the screencast of the issue through email, hence adding Needs-Feedback label to it.

Thanks!

Comment 11 by sharonab...@gmail.com, Yesterday (44 hours ago) 

Thanks viswa.karala, I responded to your message.
Project Member

Comment 12 by sheriffbot@chromium.org, Yesterday (44 hours ago)

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 13 by viswa.karala@chromium.org, Today (23 hours ago)

Labels: Needs-Feedback
Unable to reproduce the issue on chrome reported version# 72.0.3626.53 using Windows-10, shared the screencast of the issue through email.

Thanks!
►

Sign in to add a comment