Search the archives!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Javascript] Memory leaks?
- From: elmuchacho at gmail.com (Laurent Muchacho)
- Subject: [Javascript] Memory leaks?
- Date: Mon Apr 24 04:09:56 2006
Hi Scott, This is not an easy thing to sort out and to understand properly where you code might leak it require a lot of reading on your part. I had similar problem a little while ago and the link below it is what I will recommend This is a tool call drip and it is really good and help a lot however it doesn't always found the link when you make them obvious and want to show your mate (it happen to me) http://outofhanwell.com/ieleak/index.php?title=Main_Page The first article is pretty good and the second one is from the people who made leak something we have to worry about. http://laurens.vd.oever.nl/weblog/items2005/closures/ http://msdn.microsoft .com/library/default.asp?url=/library/en-us/IETechCol/dnwebgen/ie_leak_patterns.asp Even if this article refer to IE they make good references on not what to do in all browser I hope this help good luck Laurent On 4/22/06, Scott Reynen <scott@xxxxxxxxxxxxxxx> wrote: > > I have a few AJAX applications, which work fine in IE, Firefox, and > Safari, pinging the server every few seconds for new data. I've > noticed that if I leave one of these applications open overnight in > Safari (haven't tested this in anything else yet), the key event > handling will slow to a crawl by morning and it will only register > that I've typed something a second or two after I actually press the > key. When I first open the application, such typing will register > immediately. Even if I reload the page after this happens, it will > still be slow until I actually restart the whole browser. > > I'm not clear on what's causing this, but it seems like a memory > leak. Here are two applications that both seem to cause this problem: > > http://randomchaos.com/games/fastr/js/chat.js > http://randomchaos.com/games/fastr/js/group.js > > The both involve typing in a text input, and they both take specific > actions on the return/enter (13) keypress. Unfortunately, you won't > be able to experience the problem yourself with registering and > leaving it open for several hours. I'm sure there are a hundred > problems with this code, as I'm largely self-taught in JavaScript. > I'm specifically interested in the problem I described above, and > would appreciate any suggestions in preventing such a gradual > slowdown of the event handling. > > Peace, > Scott > _______________________________________________ > Javascript mailing list > Javascript@xxxxxxxxxx > https://lists.LaTech.edu/mailman/listinfo/javascript > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.LaTech.edu/pipermail/javascript/attachments/20060424/47a355bf/attachment.html
- Follow-Ups:
- [Javascript] Memory leaks?
- From: Steve Clay
- [Javascript] Memory leaks?
- References:
- [Javascript] Memory leaks?
- From: Scott Reynen
- [Javascript] Memory leaks?
- Prev by Date: [Javascript] Memory leaks?
- Next by Date: [Javascript] window.close () not catched
- Previous by thread: [Javascript] Memory leaks?
- Next by thread: [Javascript] Memory leaks?
- Index(es):