window.navigator.webkitGetUserMedia taking too much time to respond in nwjs 0.59.2

[rakesh-anchan]

Thanks for reporting an issue! Spend 60 seconds reading this...

1. Before reporting, try reproducing against the latest version of NWJS.

2. Issue tracker is only for bugs and feature requests, in English only.

   Anything else? Use our mailing list for questions: https://groups.google.com/forum/#!forum/nwjs-general

======== TEMPLATE BUG FORM ========

NWJS Version : v0.59.2 Operating System : Windows10

Expected behavior

webkitGetUserMedia should not take more than , 300ms

Actual behavior

window.navigator.webkitGetUserMedia taking too much time to respond in nwjs 0.59.2 intermittently. We have noticed delay of 10- 15 minutes in getting streams

Note: This was working fine in v0.45.7

How to reproduce

• Open nwjs sdk for v0.59.2

• Open developer tool and console

• Run below code snippet var startTime = new Date(); console.info(startTime); window.navigator.webkitGetUserMedia({"video":false, "audio":true}, function(stream){ endTime = new Date() console.info('Stream', stream, [endTime-startTime+"ms"]) }, function(err){ console.info("error")});

• Same behavior is seen in v0.66.0 as well

[ayushmanchhabra]

Thanks for opening the issue in the chromium bug tracker. Linking this here for better visibility: https://bugs.chromium.org/p/chromium/issues/detail?id=1343275&q=webkitGetUserMedia&can=2

[ayushmanchhabra]

@rakesh-anchan I used v0.66.1 and consistently got less than 300ms.

Steps to reproduce:

1. If you don't have Node installed, use volta or nvm
2. On Node v16.16.0, launch this demo app by executing npm start
3. Right click and choose Inspect background page to open DevTools
4. Run the above mentioned code snippet in the Console

[rakesh-anchan]

@ayushmxn With our further analysis on the issue, we found that, api takes more time, if the nodewebkit main window is in minimized state.

When we move the window to foreground, we get the response.

[ayushmanchhabra]

~That's weird! Is it possible to make a small repro so I can dig into this? Seems NW.js related.~

Try making the API call from the Node context if you haven't already.

[rakesh-anchan]

I have attached video of reproducing the issue win v0.66.0 version

[ayushmanchhabra]

Thanks! I was able to reproduce on my end. Looks like the behaviour of getUserMedia was recently changed. I believe a workaround would be to use the Node context. As you see here, there is no issue when I run the code snippet in the background page (Node context).

[ayushmanchhabra]

@rakesh-anchan were you able to find a workaround?

[rakesh-anchan]

@ayushmxn No, we could not get the workaround and ticket (https://bugs.chromium.org/p/chromium/issues/detail?id=1343275&q=webkitGetUserMedia&can=2) which we raised in chromium site, says that, it is behavioral change done on chromium to meet the media feature compliance.

As of now we had to change the behavior in our application, whenre application was brought to focus before calling webkitgetusermedia api.

[fippo]

Have you tried adding the blink-features option to the command line args? It is a allowlisted flag here and the process is documented here

[ayushmanchhabra]

@rakesh-anchan I'll be afk till Monday if you want to give this a go. This looks promising given this comment on the Chromium ticket.

[ayushmanchhabra]

I get a DOMException: Requested device not found error on adding the disable blink feature flag so unable to confirm if it works.

[ayushmanchhabra]

@rakesh-anchan upstream ticket comment 16 may help

[MistakingManx]

I am experiencing this issue, my solution since it's for Windows only, was to use "nircmd" to focus the window when it needs to listen, nir win activate process nw.exe.

Is there a better method, though?