Extension native messaging problem

[tudor ciucas]

Hi,

I'm developing a Chrome Extension and a Windows application written in C++. The extension starts this application at the start-up of a web-page. I used chrome.runtime.connectNative to open my Windows application, and chrome.tabs.sendMessage to communicate with it. In the C++ application, I'm using standard input (stdin) and standard output (stdout) to receive and send messages to the extension. So far so good, but, the problem is that after some time (even if I'm idle) the port closes by itself. No error, no exception. Nothing. And I have no idea why this happens. 

Maybe someone can give me more information about that? I'm not sure which are all the cases when the extension is closing the port and why (I designed my C++ application to close itself when the connection is lost).

I would be grateful for every piece of information you would assist me with. Thank you

[gaurav kaushal]

Hi Tudor, I'm also experiencing maybe something similar by reading your problem I'm my application we are using Native messaging to communicate between browser and printer but somehow after chrome release 65 or can say that after April 2018 we started facing an issue when we are in lull state. Some of the print not getting intermittently.

[tudor ciucas]

I found out that if everything is idle, if the extension is not sending anything to the native application, then the native application will receive EOF and will close itself. But for moment i don't really know why it receives EOF