You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/05/12 23:58:45 UTC
[jira] Created: (TAP5-1147) Ajax updated under IE leak lots of
memory
Ajax updated under IE leak lots of memory
-----------------------------------------
Key: TAP5-1147
URL: https://issues.apache.org/jira/browse/TAP5-1147
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.2.0
Reporter: Howard M. Lewis Ship
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-1147) Ajax updates under IE leak lots of
memory
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1147.
--------------------------------------
Fix Version/s: 5.2.0
Resolution: Fixed
> Ajax updates under IE leak lots of memory
> -----------------------------------------
>
> Key: TAP5-1147
> URL: https://issues.apache.org/jira/browse/TAP5-1147
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Critical
> Fix For: 5.2.0
>
>
> When an Ajax update changes content on a page, IE wil leak the old DOM nodes under many circumstances. If the DOM nodes have event handlers that are closures that hold a reference back to the DOM node (very easy to do, even without meaning to) a leak will ensue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-1147) Ajax updates under IE leak lots of
memory
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1147.
--------------------------------------
Fix Version/s: 5.2.0
Resolution: Fixed
> Ajax updates under IE leak lots of memory
> -----------------------------------------
>
> Key: TAP5-1147
> URL: https://issues.apache.org/jira/browse/TAP5-1147
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Critical
> Fix For: 5.2.0
>
>
> When an Ajax update changes content on a page, IE wil leak the old DOM nodes under many circumstances. If the DOM nodes have event handlers that are closures that hold a reference back to the DOM node (very easy to do, even without meaning to) a leak will ensue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-1147) Ajax updates under IE leak lots of
memory
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-1147:
---------------------------------------
Summary: Ajax updates under IE leak lots of memory (was: Ajax updated under IE leak lots of memory)
Assignee: Howard M. Lewis Ship
Priority: Critical (was: Major)
Notes on it:
http://www.outofhanwell.com/ieleak/index.php?title=Main_Page
http://javascript.crockford.com/memory/leak.html
this problem has been around for a while.
The right course of action is to be careful about anything deleted from the DOM. It is necessary to delete any attributes that look like functions (i.e., onclick or onevent attributes) as well as use Prototype's APIs to delete any event handler functions. Only then do the memory leaks disappear.
Fortunately, I had some time to work through this for a client.
> Ajax updates under IE leak lots of memory
> -----------------------------------------
>
> Key: TAP5-1147
> URL: https://issues.apache.org/jira/browse/TAP5-1147
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Critical
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-1147) Ajax updates under IE leak lots of
memory
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-1147:
---------------------------------------
Labels: ie javascript (was: )
Description: When an Ajax update changes content on a page, IE wil leak the old DOM nodes under many circumstances. If the DOM nodes have event handlers that are closures that hold a reference back to the DOM node (very easy to do, even without meaning to) a leak will ensue.
> Ajax updates under IE leak lots of memory
> -----------------------------------------
>
> Key: TAP5-1147
> URL: https://issues.apache.org/jira/browse/TAP5-1147
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Critical
>
> When an Ajax update changes content on a page, IE wil leak the old DOM nodes under many circumstances. If the DOM nodes have event handlers that are closures that hold a reference back to the DOM node (very easy to do, even without meaning to) a leak will ensue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-1147) Ajax updates under IE leak lots of
memory
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-1147:
---------------------------------------
Labels: ie javascript (was: )
Description: When an Ajax update changes content on a page, IE wil leak the old DOM nodes under many circumstances. If the DOM nodes have event handlers that are closures that hold a reference back to the DOM node (very easy to do, even without meaning to) a leak will ensue.
> Ajax updates under IE leak lots of memory
> -----------------------------------------
>
> Key: TAP5-1147
> URL: https://issues.apache.org/jira/browse/TAP5-1147
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Critical
>
> When an Ajax update changes content on a page, IE wil leak the old DOM nodes under many circumstances. If the DOM nodes have event handlers that are closures that hold a reference back to the DOM node (very easy to do, even without meaning to) a leak will ensue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-1147) Ajax updates under IE leak lots of
memory
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-1147:
---------------------------------------
Summary: Ajax updates under IE leak lots of memory (was: Ajax updated under IE leak lots of memory)
Assignee: Howard M. Lewis Ship
Priority: Critical (was: Major)
Notes on it:
http://www.outofhanwell.com/ieleak/index.php?title=Main_Page
http://javascript.crockford.com/memory/leak.html
this problem has been around for a while.
The right course of action is to be careful about anything deleted from the DOM. It is necessary to delete any attributes that look like functions (i.e., onclick or onevent attributes) as well as use Prototype's APIs to delete any event handler functions. Only then do the memory leaks disappear.
Fortunately, I had some time to work through this for a client.
> Ajax updates under IE leak lots of memory
> -----------------------------------------
>
> Key: TAP5-1147
> URL: https://issues.apache.org/jira/browse/TAP5-1147
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Critical
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.