You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tolmasky opened this issue
Aug 20, 2015
· 4 comments
Labels
c++Issues and PRs that require attention from people who are familiar with C++.libuvIssues and PRs related to the libuv dependency or the uv binding.questionIssues that look for answers.
In node.cc immediately after LoadEnvironment() in Start()it jumps to:
more = uv_run(env->event_loop(), UV_RUN_ONCE);
I understand why it's UV_RUN_ONCE on each iteration of the loop, not why it starts that way. I imagine there are some default events that happen no matter what the first time through, could someone enlighten me as to what those are (that stop node from just blocking forever)?
The text was updated successfully, but these errors were encountered:
Fishrock123
added
question
Issues that look for answers.
c++
Issues and PRs that require attention from people who are familiar with C++.
libuv
Issues and PRs related to the libuv dependency or the uv binding.
labels
Aug 20, 2015
Possibly -- I guess I'm confused why process._getActiveHandles() returns an empty array right before it enters this initial uv_run (causing me to believe that uv_run would block forever). Do ticks not count as handles in this sense?
c++Issues and PRs that require attention from people who are familiar with C++.libuvIssues and PRs related to the libuv dependency or the uv binding.questionIssues that look for answers.
In node.cc immediately after LoadEnvironment() in Start()it jumps to:
I understand why it's UV_RUN_ONCE on each iteration of the loop, not why it starts that way. I imagine there are some default events that happen no matter what the first time through, could someone enlighten me as to what those are (that stop node from just blocking forever)?
The text was updated successfully, but these errors were encountered: