randy marmer
2005-Nov-20 02:23 UTC
Prototype, "periodically_call_remote" throws CPU into overdrive... ?!?
Hello, 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 100%!!? 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 & exit... at startup i get a series of JS warnings from prototype. Then the "periodically_call_remote" call starts firing - without (apparent) 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: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIXMLHttpRequest.status]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: http://localhost:3000/javascripts/prototype.js :: anonymous :: line 678" data: no] Source File: http://localhost:3000/javascripts/prototype.js Line: 678 ===================================================== & then it can take up to 30 secs or more for cpu to rev back down after app exit!! 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 excessive? Doesn''t the series of the same error on exit indicate something very wrong? I have not been able to find mention of this type of problem anywhere. Any wisdom would be greatly appreciated! Thanks much! Randy __________________________________ Yahoo! Mail - PC Magazine Editors'' Choice 2005 http://mail.yahoo.com