Forum: Ruby on Rails Prototype, "periodically_call_remote" throws CPU into overdr

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Randy M. (Guest)
on 2005-11-20 04:24
(Received via mailing list)

im playing around with "periodically_call_remote"
(frequency 1 sec) & even when i have it call an
empty "dummy" method it revs up my cpu to almost

i'm running Rails 0.13.1, Ruby 1.8, on a OS X 10.3.9
on a G5 w/
Firefox & i've alternated btw Prototype 1.3.0 &
1.4.0_rc2 with almost identical results.

Using the dummy call (frequency 1 sec) with Prototype
1.4.0_rc2 & checking JS errors at app startup &
at startup i get a series of JS warnings from

Then the "periodically_call_remote" call starts firing
- without
incident - but the cpu revs way up into the 90's!!

Then when i exit the app i get a whole slew of a
particular error;


Error: [Exception... "Component returned failure code:
[nsIXMLHttpRequest.status]"  nsresult: "0x80040111
(NS_ERROR_NOT_AVAILABLE)"  location: "JS frame ::
http://localhost:3000/javascripts/prototype.js ::
anonymous :: line 678"  data: no]
Source File:
Line: 678


& then it can take up to 30 secs or more for cpu to
rev back down after app

Has anyone seen this error before or experienced such
a problem?

Any callback to the server surely entails a CPU hit,
but isn't this

Doesn't the series of the same error on exit indicate
something very

I have not been able to find mention of this type of
problem anywhere. Any wisdom would be greatly

Thanks much!


Yahoo! Mail - PC Magazine Editors' Choice 2005
This topic is locked and can not be replied to.