Uses a lot of CPU

[wmertens]

When NiM is in auto mode, I can often see it take up 15% of CPU in the Chrome task manager. Can this not be lessened?

Even when I switch to manual mode, the extension takes up 0.1% CPU even though it shouldn't be doing anything…

(BTW, great extension! 👍 🙇)

[june07]

Thank you for the feedback.

I could definitely use some help, so feel free to issue a PR for the fix. ;)

[wmertens]

:) any idea what could cause it?

…

On Thu, Aug 3, 2017, 1:11 PM Will ***@***.***> wrote: Thank you for the feedback. I could definitely use some help, so feel free to issue a PR for the fix. ;) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#20 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADWlibNjDQxZqx2T7AD1Df_jTVWDilyks5sUarNgaJpZM4OnU0T> .

[june07]

The only thing I can think of off hand is the polling. I wrote a back off function but still that might be the issue. I haven't had a chance to try to duplicate the problem yet myself.

…

On Aug 3, 2017 8:06 AM, "Wout Mertens" ***@***.***> wrote: :) any idea what could cause it? On Thu, Aug 3, 2017, 1:11 PM Will ***@***.***> wrote: > Thank you for the feedback. > > I could definitely use some help, so feel free to issue a PR for the fix. > ;) > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/june07/Node.js-inspector-Manager-NiM- /issues/20#issuecomment-319939754>, > or mute the thread > <https://github.com/notifications/unsubscribe- auth/AADWlibNjDQxZqx2T7AD1Df_jTVWDilyks5sUarNgaJpZM4OnU0T> > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#20 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AK099hNRybWosNreT6fJsP5m8hdptvpPks5sUeH_gaJpZM4OnU0T> .

[wmertens]

In the mean time, Chrome built-in inspector detection got good, and I haven't needed NiM any more… Thank you for your work!

[wmertens]

In the meantime, Chrome has gotten very good at Node debugging, and I don't need this extension any more. Chrome doesn't seem to suffer from CPU usage while polling. To use it, go to chrome://inspect and click on the "dedicated devtools for chrome" link. There, in the connections tab, you can specify hosts and ports, I only tried with localhost. When you're running node with --inspect, you can either go to chrome://inspect or you should be able to click on a little node icon in the top left of the web devtools. Thank you for the work you put in this extension, it was very nice to have it!

…

On Sat, Aug 5, 2017 at 6:23 AM Will ***@***.***> wrote: The only thing I can think of off hand is the polling. I wrote a back off function but still that might be the issue. I haven't had a chance to try to duplicate the problem yet myself. On Aug 3, 2017 8:06 AM, "Wout Mertens" ***@***.***> wrote: > :) any idea what could cause it? > > On Thu, Aug 3, 2017, 1:11 PM Will ***@***.***> wrote: > > > Thank you for the feedback. > > > > I could definitely use some help, so feel free to issue a PR for the fix. > > ;) > > > > — > > You are receiving this because you authored the thread. > > Reply to this email directly, view it on GitHub > > <https://github.com/june07/Node.js-inspector-Manager-NiM- > /issues/20#issuecomment-319939754>, > > or mute the thread > > <https://github.com/notifications/unsubscribe- > auth/AADWlibNjDQxZqx2T7AD1Df_jTVWDilyks5sUarNgaJpZM4OnU0T> > > . > > > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > < #20 (comment) >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/AK099hNRybWosNreT6fJsP5m8hdptvpPks5sUeH_gaJpZM4OnU0T > > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#20 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADWlofowv636Bwwe2HmTLMqsXvE0Wwwks5sU-5dgaJpZM4OnU0T> .