If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Native Message Host fails to return a response when called in rapid succession.

RESOLVED INCOMPLETE

Status

()

Toolkit
WebExtensions: Untriaged
RESOLVED INCOMPLETE
a year ago
5 months ago

People

(Reporter: makeen, Unassigned)

Tracking

51 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

a year ago
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36

Steps to reproduce:

In a for loop I make calls into the native message host (nmh). This creates promises that should resolve as soon as the nmh sends the response.


Actual results:

No response is ever returned. I printed out the messages (in my native code) and the messages were jammed together in the buffer. The reading of the messages was failing since it would hit unexpected bytes when trying to read. Also, the length of the incoming message was huge since the messages were jammed together.


Expected results:

Each message from the extension code should be sent individually to the native code. The native code should read and process that message only. Also, I confirmed that my code works as expected in Chrome using the native message host.

Updated

6 months ago
Component: Activity Streams: General → Untriaged

Updated

6 months ago
Component: Untriaged → WebExtensions: Untriaged
Product: Firefox → Toolkit
Can you please provide a testcase extension and app for this?
We have tests for this type of behavior, so marking as incomplete until we have a testcase. Please reopen if you can provide one.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.