search

basecamp / pow

Zero-configuration Rack server for Mac OS X
http://pow.cx/
MIT License
3.4k stars 261 forks source link

Pow is running 99% of my CPU usage #99

Closed stephenson closed 12 years ago

stephenson commented 13 years ago

... and the app dos not work.

Pow error

eddorre commented 13 years ago

I run into at least twice a day and sometimes back to back (after killing and restarting the pow process). Looking forward to testing this out.

abachman commented 13 years ago

Thanks for staying on this @sstephenson, I've been digging pow and recommending it to other devs.

I'll post a backtrace if anything comes up.

morganick commented 13 years ago

@sstephenson Just made it through my second day without this problem after updating to 0.4.0-pre. I'm hearing similar results from others in the office.

Thanks for all of your hard work.

jimryan commented 13 years ago

Yes @sstephenson same here, second day without this problem. Thank you so much for resolving this!

kylemathews commented 13 years ago

0.4.0-pre is working great for me so far too. Nice job! It's great to be using pow again.

davetheninja commented 13 years ago

Just installed the 0.4.0-pre.

Fingers crossed!

jimryan commented 13 years ago

I've been running 0.4.0-pre since it was released and it was running great until Friday when I ran into the issue again. I was rushing to get some work done and killed it before thinking. If it happens again I'll be sure to post a trace.

Jim On Oct 8, 2011 11:54 PM, "Dave the Ninja" < reply@reply.github.com> wrote:

Just installed the 0.4.0-pre.

Fingers crossed!

Reply to this email directly or view it on GitHub: https://github.com/37signals/pow/issues/99#issuecomment-2335114

semaperepelitsa commented 13 years ago

I haven't installed 0.4 since this happens rarely to me. Here is my backtrace for 0.3.2:

#00 dn_find(src=#<Buffer>, domain=0, msg=#<Buffer>, dnptrs=#<Array>, ndnptr=0, lastdnptr=2) /usr/local/Cellar/pow/0.3.2/pow/node_modules/ndns/lib/ndns.js line 1109 column 4 (position 25436)
#01 ns_name_pack(src=#<Buffer>, srcn=0, dst=#<Buffer>, dstn=23, dstsiz=65512, dnptrs=#<Array>, lastdnptr=25) /usr/local/Cellar/pow/0.3.2/pow/node_modules/ndns/lib/ndns.js line 832 column 8 (position 20326)
#02 ns_newmsg_rr(handle=#<ns_newmsg>, sect=1, name=#<Buffer>, type=1, rr_class=1, ttl=600, rdlen=4, rdata=#<Buffer>) /usr/local/Cellar/pow/0.3.2/pow/node_modules/ndns/lib/ndns.js line 1663 column 6 (position 37192)
#03 #<ServerResponse>.writeOnce(buf=#<Buffer>, bufsiz=65535) /usr/local/Cellar/pow/0.3.2/pow/node_modules/ndns/lib/ndns.js line 2526 column 9 (position 56322)
#04 #<ServerResponse>.sendTo(socket=#<DnsServer>, port=50233, host=127.0.0.1) /usr/local/Cellar/pow/0.3.2/pow/node_modules/ndns/lib/ndns.js line 2540 column 16 (position 56623)
#05 #<ServerResponse>.send() /usr/local/Cellar/pow/0.3.2/pow/node_modules/ndns/lib/ndns.js line 2605 column 7 (position 58077)
#06 #<DnsServer>.handleRequest(req=#<ServerRequest>, res=#<ServerResponse>) /usr/local/Cellar/pow/0.3.2/pow/lib/dns_server.js line 37 column 18 (position 1656)
#07 #<DnsServer>.handleRequest(#<ServerRequest>, #<ServerResponse>) /usr/local/Cellar/pow/0.3.2/pow/lib/dns_server.js line 3 column 63 (position 162)
#08 #<DnsServer>.emit(type=request, #<ServerRequest>, #<ServerResponse>) events.js line 67 column 17 (position 2560)
#09 #<DnsServer>.messageListener(msg=#<Buffer>, rinfo=#<Object>) /usr/local/Cellar/pow/0.3.2/pow/node_modules/ndns/lib/ndns.js line 2640 column 8 (position 58884)
alexlod commented 13 years ago

I've been using Pow in total for just 3 days. I upgraded to 0.4.0-pre a minute ago. It's running flawlessly. Thanks!

thegrubbsian commented 12 years ago

I am having this CPU issue intermittently. I'm running on Node 0.4.12 and it's happened off and on since 0.4.0. Has pow been tested with 0.6.0? Any chance an upgrade would fix this issue?

rbazinet commented 12 years ago

I have been plagued by this issue for a while now, updated to 0.4.0-pre a couple weeks ago and it is running flawlessly. I have not had to kill pow manually since.

I just figured I would give that feedback.

nifl commented 12 years ago

I had this issue affecting a POW install on my previous laptop. One afternoon I stepped away from my machine for several hours and returned to a fried logic board. I can't be certain POW caused the issue but considering I was having frequent issues with it going nutso, it's suspect. If it is the cause, then this issue is serious and the name "pow" is perfect.

sankroh commented 12 years ago

Happened to me with 0.3.2 (cpu pegged at 100%) but not so far with 0.4.0-pre.

cabgfx commented 12 years ago

I've had this issue for a while, on seemingly random occassions. Sometimes, pow is just slow (not just when the process is idle), but doesn't always ramp up the CPU usage. Activity Monitor > Force Quit pow always fixes it, I've never experienced issues where the computer locked up.

I use the powder gem, as well as:

I'm a bit unsure about how to provide a stack-trace or similar debugging aids?

Thanks for an awesome piece of software, btw! :thumbsup:

eddorre commented 12 years ago

@cabgfx,

Use the 0.4.0-pre release.

curl get.pow.cx | VERSION=0.4.0-pre sh

eddorre commented 12 years ago

@sstephenson I think it might be time to release the 0.4.0-pre release as the main release.

The 0.3.2 release is clearly broken yet the documentation on the site still refers to this version. It seems to be confusing people that are new to the project.

The 0.4.0-pre release has been tested by working developers for 5 months.

Judging from the lack of comments about the 0.4.0-pre release in here, I would say that it's pretty stable.

What's the chance of cutting a 0.4.0 release and making that the official version soon?

semaperepelitsa commented 12 years ago

0.4.0-pre works fine for me, +1 for releasing it.

hmans commented 12 years ago

:+1: for releasing 0.4.0!

tanordheim commented 12 years ago

Been running 0.4.0-pre for several months now to get around these issues, haven't had any problems what so ever. +1 for releasing 0.4.0.

cabgfx commented 12 years ago

@eddorre - thanks, I'll be sure to post back with how it works out.

jimryan commented 12 years ago

+1 Been running solid for months as well. Much more stable than current release.

cabgfx commented 12 years ago

Running on 0.4.0-pre for the past 4 days seems to have killed all issues mentioned earlier in thread! Thanks :heart:

bashcoder commented 12 years ago

So glad I discovered this thread and upgraded to 0.4.0-pre. I had been having a lot of what @cabgfx describes, and the runway processes described elsewhere here.

I was back to webrick and wearing out ctrl-c. Now I can resume using https://github.com/guard/guard-pow

I echo recommendations to release this as the current release version. This is issue #99 on this project and it used 99% of my CPU. So I guess I could say that I had "99 problems, but this glitch ain't one." (yes, that just happened.)

chapati23 commented 12 years ago

+1 for 0.4.0

JeanMertz commented 12 years ago

I wonder why this hasn't been released as 0.4.0 as well. I'd like to install pow through homebrew, but it only supports the latest 0.3.2.

robert-stuttaford commented 12 years ago

"Pow is a zero-config Rack server for Mac OS X. Have it serving your apps locally in under a minute."

suuuuuure it will. you weren't clear that this 'minute' was on the arse-end of an hour's worth of hunt-the-bugfix!

+1 billionty billion: release 0.4 as final.

DouweM commented 12 years ago

Another +1 for releasing 0.4.0 as final. The 99% issue had been occurring multiple times a day for me, and since installing 0.4.0-pre everything's been fine.

derek-watson commented 12 years ago

+1 Eleventy Billion

onetruth commented 12 years ago

Ah, thnx for the 0.4.0-pre. POW was running fine until recently, which led me here. Thanks!

supermarin commented 12 years ago

Updated POW, still have the problem after the system wakes up from sleep. Reproduced it 2 times yesterday/today