OK, I have an app that uses the periodic updater to to check on the server if any new orders have come in. It works great, but I notice if I leave this window open for a long time Firefox starts to become slow and unresponsive. Is there a known memory issue with using this? If not whats the best way to track down what is causing it. Thanks. ______________________________________________________________________ Alex Duffield --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Without seeing some code, it''s tough to say for sure, but the first thing I''d check for is whether you might be recreating your updater in the callback from the AJAX request. If so, every time you check, you''ll double up the number of requests you''re making, which will lead to trouble, but won''t be hugely noticeable until it''s run a good number of times. The easiest thing to do is to use Firefox, along with: 1) Firebug to watch the AJAX requests coming and going, to make sure they''re being called only as often as you think they are and 2) The web developer toolkit. Use the view source->generated source (perhaps along with a diff tool) to make sure your generated html isn''t getting bigger with every request -Jerod On 5/23/07, Alex Duffield <Alex-GLL9njBnHiGqPKKiFzS5XxZCeNDtXRbv@public.gmane.org> wrote:> > > OK, I have an app that uses the periodic updater to to check on the > server if any new orders have come in. > > It works great, but I notice if I leave this window open for a long > time Firefox starts to become slow and unresponsive. > > Is there a known memory issue with using this? If not whats the best > way to track down what is causing it. > > Thanks. > ______________________________________________________________________ > Alex Duffield > > > > > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Thanks, Ya, I am using both of those firefox extensions. .. (can one develop with out them??) Request is just getting called once every 30 seconds as it should be. And the resulting HTML code is as per expectation. When I was testing I had it set to fire every 2 seconds so I would never have to wait to see and new order coming in... that is when I started noticing the slow down.. In reality it will probably be set 5 - 10 minutes so it probably wont be a major deal breaker, I just dont like leaving things like that un resolved in my code!!. ______________________________________________________________________ Alex Duffield ❖ Principal ❖ InControl Solutions . http:// www.incontrolsolutions.com On 23-May-07, at 3:03 PM, Jerod Venema wrote:> Without seeing some code, it''s tough to say for sure, but the first > thing I''d check for is whether you might be recreating your updater > in the callback from the AJAX request. If so, every time you check, > you''ll double up the number of requests you''re making, which will > lead to trouble, but won''t be hugely noticeable until it''s run a > good number of times. > > The easiest thing to do is to use Firefox, along with: > > 1) Firebug to watch the AJAX requests coming and going, to make > sure they''re being called only as often as you think they are > > and > > 2) The web developer toolkit. Use the view source->generated source > (perhaps along with a diff tool) to make sure your generated html > isn''t getting bigger with every request > > -Jerod > > > On 5/23/07, Alex Duffield <Alex-GLL9njBnHiGqPKKiFzS5XxZCeNDtXRbv@public.gmane.org> wrote: > > OK, I have an app that uses the periodic updater to to check on the > server if any new orders have come in. > > It works great, but I notice if I leave this window open for a long > time Firefox starts to become slow and unresponsive. > > Is there a known memory issue with using this? If not whats the best > way to track down what is causing it. > > Thanks. > ______________________________________________________________________ > Alex Duffield > > > > > > > > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
altay-6c8tSettBfPPIjl8wruziA@public.gmane.org
2007-May-24 20:37 UTC
Re: periodic updater and mem leaks...
While Firebug is the best extension *ever*, and I don''t know how I''d get anything done without it... hate to say it, but that might be the source of your problem. Googling "firebug memory leak" or something along those lines will reveal lots of vague reports of it eating up memory (e.g., http://groups.google.com/group/firebug/browse_thread/thread/845a6eda868b31be/1331412051bd4112%231331412051bd4112 ). I''ve noticed, too, that if I leave Firebug enabled in any page that does periodical ajax, like gmail or ajaxMyTop, Firefox leaks a ton. If I disable Firebug in that page, everything''s fine -- no leaks. So I''d try disabling Firebug and seeing if you still have the leak problem. The ''Bug is so damn useful that I wouldn''t recommend uninstalling it... the key is keeping it disabled until you actually need to use it. I''ve been a much happier Firefox user since I''ve picked up this habit! Altay On May 23, 11:20 pm, Alex Duffield <A...-GLL9njBnHiGqPKKiFzS5XxZCeNDtXRbv@public.gmane.org> wrote:> Thanks, Ya, I am using both of those firefox extensions. .. (can one > develop with out them??) > > Request is just getting called once every 30 seconds as it should be. > And the resulting HTML code is as per expectation. > > When I was testing I had it set to fire every 2 seconds so I would > never have to wait to see and new order coming in... that is when I > started noticing the slow down.. In reality it will probably be set 5 > - 10 minutes so it probably wont be a major deal breaker, I just dont > like leaving things like that un resolved in my code!!. > > ______________________________________________________________________ > Alex Duffield ❖ Principal ❖ InControl Solutions . http://www.incontrolsolutions.com > > On 23-May-07, at 3:03 PM, Jerod Venema wrote: > > > Without seeing some code, it''s tough to say for sure, but the first > > thing I''d check for is whether you might be recreating your updater > > in the callback from the AJAX request. If so, every time you check, > > you''ll double up the number of requests you''re making, which will > > lead to trouble, but won''t be hugely noticeable until it''s run a > > good number of times. > > > The easiest thing to do is to use Firefox, along with: > > > 1) Firebug to watch the AJAX requests coming and going, to make > > sure they''re being called only as often as you think they are > > > and > > > 2) The web developer toolkit. Use the view source->generated source > > (perhaps along with a diff tool) to make sure your generated html > > isn''t getting bigger with every request > > > -Jerod > > > On 5/23/07, Alex Duffield <A...-GLL9njBnHiGqPKKiFzS5XxZCeNDtXRbv@public.gmane.org> wrote: > > > OK, I have an app that uses the periodic updater to to check on the > > server if any new orders have come in. > > > It works great, but I notice if I leave this window open for a long > > time Firefox starts to become slow and unresponsive. > > > Is there a known memory issue with using this? If not whats the best > > way to track down what is causing it. > > > Thanks. > > ______________________________________________________________________ > > Alex Duffield--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---