-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
100% (single) core load on Windows #1308
Comments
possibly related to #1221 |
100% related
…On Wed, Aug 23, 2017 at 3:57 PM Volodymyr Shymanskyy < ***@***.***> wrote:
possibly related to #1221
<#1221>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1308 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABlbvKMZSOa-keJ-AgLkh5X0FABwDnnks5sbIQYgaJpZM4PAfqj>
.
|
Ok, good to know. But putting 100% load on one core is weird - I would expect minor load increase due to sync. operation (and, of course thread count limitation). |
We're not doing it right, in any case. Your trace shows the read process
is being called.
…On Thu, Aug 24, 2017, 3:48 AM Volodymyr Shymanskyy ***@***.***> wrote:
Ok, good to know. But putting 100% load on one core is weird - I would
expect minor load increase due to sync. operation (and, of course thread
count limitation).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1308 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABlbqMRmbznRg40IL13cMfbJShe03cWks5sbSqvgaJpZM4PAfqj>
.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
SerialPort v5.0.0
Node version is v7.9.0
Electron version is 1.7.5
Windows 10 (32-bit)
Summary of Problem
On Windows, once a serial port is opened (manufacturer:"wch.cn", vid:"1A86", pid:"7523"),
I experience 100% (single) core load on Windows. On Linux, the same app produces nearly 0 load.
Using Process Monitor, I obtained a stacktrace of the busy thread:
The text was updated successfully, but these errors were encountered: