Ticket #7045 (closed bug: patchwelcome)
Memory leaks when using events and iframes
| Reported by: | Aule | Owned by: | |
|---|---|---|---|
| Priority: | high | Milestone: | 1.5 |
| Component: | unfiled | Version: | 1.5 |
| Keywords: | iframe events | Cc: | paw.zubr@… |
| Blocking: | Blocked by: |
Description
Please check TC: http://pz16.info/a.html
I checked it in Opera and in Chrome. On both browsers memory usage grow when test was ran.
I think it's something with unbinding events from elements in iframes when using empty() method, because when added explicit unbind() before emptying iframe there is no memory leak.
Change History
comment:2 Changed 3 years ago by snover
- Priority set to high
- Status changed from new to open
- Milestone changed from 1.4.2 to 1.next
comment:3 Changed 3 years ago by Aule
Check jsFiddle: http://jsfiddle.net/R2PM7/
comment:4 Changed 3 years ago by snover
- Milestone changed from 1.4.4 to 1.4.5
Retargeting due to severity of regressions in 1.4.3.
comment:5 Changed 3 years ago by snover
- Milestone changed from 1.4.5 to 1.4.4
Retargeting for 1.4.4 as per John’s request.
comment:6 Changed 3 years ago by dmethvin
- Owner set to dmethvin
- Status changed from open to assigned
comment:7 Changed 3 years ago by dmethvin
- Owner dmethvin deleted
- Status changed from assigned to open
The resolution of this ticket seems tricky. If we attach events to the iframe's document elements and the user later navigates to another domain, we need to catch that and release them before it happens.
comment:8 Changed 3 years ago by snover
- Milestone changed from 1.4.4 to 1.4.5
Punted to next minor release.
comment:9 Changed 2 years ago by dmethvin
- Status changed from open to closed
- Resolution set to patchwelcome
There are several tricky issues with dealing with cross-frame issues, including security. If someone would like to discuss them and try an implementation, let us know.
comment:10 Changed 2 years ago by john
- Version changed from 1.4.2 to 1.5
There wasn't a 1.4.5 release, was actually 1.5.
comment:11 Changed 2 years ago by john
- Milestone changed from 1.4.5 to 1.5
There was no 1.4.5 release, was actually 1.5.
comment:12 Changed 2 years ago by dmethvin
#8566 is a duplicate of this ticket.
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.

Bad milestone. There is no edit option?