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%+ CPU Usage #15

Closed
Bunn opened this Issue Mar 3, 2016 · 6 comments

Comments

Projects
None yet
3 participants
@Bunn

Bunn commented Mar 3, 2016

When running the Getting Started guide the CPU usage stays constant on 100%+ CPU usage

cpu

@dileping

This comment has been minimized.

Show comment
Hide comment
@dileping

dileping Mar 4, 2016

Member

Hi @Bunn,

thanks for reporting the issue. Could you, please, provide some more details. Like what command exactly have you executed, etc. This way I could help you better.

Thanks,
Daniel

Member

dileping commented Mar 4, 2016

Hi @Bunn,

thanks for reporting the issue. Could you, please, provide some more details. Like what command exactly have you executed, etc. This way I could help you better.

Thanks,
Daniel

@dileping dileping added the question label Mar 4, 2016

@Bunn

This comment has been minimized.

Show comment
Hide comment
@Bunn

Bunn Mar 4, 2016

Hi, @dileping
I just did the step by step instructions on the Getting Started guide.

Right after running swift-express run the CPU spikes to 100%+ and stays there.

swift-express run
Building HelloExpress in Debug mode...
Running HelloExpress...
Express was successfully launched on port 9999

Bunn commented Mar 4, 2016

Hi, @dileping
I just did the step by step instructions on the Getting Started guide.

Right after running swift-express run the CPU spikes to 100%+ and stays there.

swift-express run
Building HelloExpress in Debug mode...
Running HelloExpress...
Express was successfully launched on port 9999
@dileping

This comment has been minimized.

Show comment
Hide comment
@dileping

dileping Mar 4, 2016

Member

@Bunn ,

thanks for reporting the details! I can reproduce it now. We will fix it as soon as possible and let you know once done.

Member

dileping commented Mar 4, 2016

@Bunn ,

thanks for reporting the details! I can reproduce it now. We will fix it as soon as possible and let you know once done.

@dileping dileping added bug and removed question labels Mar 4, 2016

@dileping dileping added this to the 0.3.x: current stable milestone Mar 4, 2016

@dileping

This comment has been minimized.

Show comment
Hide comment
@dileping

dileping Mar 6, 2016

Member

@Bunn ,

thanks again for reporting the bug. It was very helpful and now it's fixed in the new major release of Express Command Line: 0.2.0.

To update to the new version, please, run:

brew update
brew upgrade swift-express

Keep in mind, that the API of command line has evolved and is slightly different now. Consider taking a look at original project page documentation: Express Command Line.

Will be very glad to hear some feedback on the new version.

Regards,
Daniel

Member

dileping commented Mar 6, 2016

@Bunn ,

thanks again for reporting the bug. It was very helpful and now it's fixed in the new major release of Express Command Line: 0.2.0.

To update to the new version, please, run:

brew update
brew upgrade swift-express

Keep in mind, that the API of command line has evolved and is slightly different now. Consider taking a look at original project page documentation: Express Command Line.

Will be very glad to hear some feedback on the new version.

Regards,
Daniel

@dileping dileping added waiting for feedback and removed bug labels Mar 6, 2016

@Bunn

This comment has been minimized.

Show comment
Hide comment
@Bunn

Bunn Mar 6, 2016

CPU Usage is now at 0.3% :)

Bunn commented Mar 6, 2016

CPU Usage is now at 0.3% :)

@Bunn Bunn closed this Mar 6, 2016

@dileping

This comment has been minimized.

Show comment
Hide comment
@dileping

dileping Mar 6, 2016

Member

@Bunn Great! Thanks for reporting back!

Member

dileping commented Mar 6, 2016

@Bunn Great! Thanks for reporting back!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment