Hi, I''m experiencing serious memory issues with my application. Mainly in FF. It''s the first time I try to locate and fix memory issues. If found drip (http://www.outofhanwell.com/ieleak/index.php? title=Main_Page). I created the most simple test page I could imagine. I also found this tool: http://blogs.msdn.com/gpde/pages/javascript-memory-leak-detector.aspx. Which is IE7 only. This is my test page: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http:// www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <script type="text/javascript" src="js/script.aculo.us/ prototype.js"></script> </head> <body> </body> </html> So as you see the only thing I have in my page is a link to prototype.js. Drip tells me that there''s a ''div'' leaking. Hmm? Just as a quick test I uncommented all places in prototype.js where a ''div'' is created. The leak is gone. Anybody? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Hi, I forgot to mention that I''m using prototype 1.6.0.2. The first place where it seems to leak is where the BrowserFeatures hash is defined. The SpecificElementExtensions key is defined using object detection. SpecificElementExtensions: document.createElement(''div'').__proto__ && document.createElement(''div'').__proto__ !=document.createElement(''form'').__proto__. Changing this to SpecificElementExtensions: false removes one of the leaks. I''m going to find out the different places in prototype where drip complains. Is this something to worry about? Manu. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Next thing. The javascript memory leak detector I mentioned in the first post told me that every time I refresh my application, there''s a ''div'' leaking. I found out that that one was caused bye the Element.cache. When I create a div using new Element(''div''), then in the Element.cache, there''s a div element stored. This leak was removed by calling "Element.cache = null;" onunload of my page. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---