Ctrl + C takes a very long time

[Globegitter]

After running broccoli serve and hitting Ctrl + C to stop the command it takes ~30 seconds until the command actually finished and the shell is responsive again.

All I did was cloning the sample app and running broccoli serve on that as-is.

[rwjblue]

This is because most of the operations are synchronous I believe.

[rwjblue]

Which means that the process exit handlers have to wait until the main thread is unlocked to run the cleanup task.

[Globegitter]

Ah ok, so this means that at least for the time being there is no simple workaround?

[rwjblue]

Correct, but I do think a fix is possible, just not a quick-fix.

[joliss]

When I hit Ctrl+C during a build (either build or serve) with current Broccoli on iojs 1.5 on Linux, it exits immediately. However it doesn't clean up tmp directories. I'd like to revisit the tmp cleanup logic when the upcoming API change is done, as it centralizes the tmp dir handling.

Getting back to the issue at hand, do you still see the "delayed exit" behavior on Mac? I actually don't remember ever seeing this problem myself, so perhaps it's platform-specific.

[stefanpenner]

mid-build cancellation PR broccolijs/broccoli#350 (forward port from ember-cli's fork) should address this.

[kylecordes]

This continues to be a surprising behavior, and something to talk around when introducing Broccoli to a new developer. Other build tool CLIs exit promptly on control-C... it would be ideal to catch up with the mainstream on this!