Skip to content
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.

Sign up for GitHub

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

Jump to bottom

process.nextTick from dev tools doesn't fire until blurred #39

Closed
kevinsawicki opened this issue Jul 15, 2013 · 1 comment
Closed

process.nextTick from dev tools doesn't fire until blurred #39

kevinsawicki opened this issue Jul 15, 2013 · 1 comment

Comments

@kevinsawicki
Copy link
Contributor

Doing the following in the dev tools will not fire until the dev tools loses focus:

process.nextTick(function() {console.log('here?')})
@zcbenz
Copy link
Member

zcbenz commented Jul 16, 2013

Node's implementation of setImmediate and process.nextTick use uv_check_start to schedule the callback to run in the next iteration of uv loop, which doesn't make atom-shell to wake up the uv loop, because it's not a real os event and would not make kevent return. I'm seeing if I can get a decent patch and send a PR to upstream libuv.

And I'll also add automatic tests for atom-shell to avoid breaking fixed bugs again.

@zcbenz zcbenz closed this as completed Jul 17, 2013
zcbenz added a commit to electron/node that referenced this issue Aug 8, 2013
@zcbenz
Guarantees that setImmediate would schedule a iteration of uv loop.
8cb0101 
setImmediate and process.nextTick use uv_check_start to schedule the callback
to run in the next iteration of uv loop, so we must make sure when setImmediate
and process.nextTick are called, a iteration of uv loop would also be scheduled.

Fixes electron/electron#39.
zcbenz added a commit to electron/node that referenced this issue Sep 5, 2013
@zcbenz
Guarantees that setImmediate would schedule a iteration of uv loop.
964562f 
setImmediate and process.nextTick use uv_check_start to schedule the callback
to run in the next iteration of uv loop, so we must make sure when setImmediate
and process.nextTick are called, a iteration of uv loop would also be scheduled.

Fixes electron/electron#39.
zcbenz added a commit to electron/node that referenced this issue Dec 5, 2013
@zcbenz
Guarantees that setImmediate would schedule a iteration of uv loop.
f79da1a 
setImmediate and process.nextTick use uv_check_start to schedule the callback
to run in the next iteration of uv loop, so we must make sure when setImmediate
and process.nextTick are called, a iteration of uv loop would also be scheduled.

Fixes electron/electron#39.
@ValeryEliseev ValeryEliseev mentioned this issue Dec 3, 2015
Closed
kevinsawicki pushed a commit that referenced this issue May 9, 2017
@aroben
Merge pull request #39 from brightray/mac-x64
7907336 
Build 64-bit on OS X
kevinsawicki pushed a commit that referenced this issue May 9, 2017
@aroben
Merge pull request #39 from brightray/mac-x64
837bd78 
Build 64-bit on OS X
@p3x-robot p3x-robot mentioned this issue Oct 3, 2018
Closed
@ckerr ckerr mentioned this issue Oct 24, 2018
Closed
This was referenced Apr 28, 2021
Merged
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zcbenz @kevinsawicki