#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@… |
| Blocked by: | Blocking: |
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 (12)
comment:1 Changed 9 years ago by
comment:2 Changed 9 years ago by
| Milestone: | 1.4.2 → 1.next |
|---|---|
| Priority: | → high |
| Status: | new → open |
comment:4 Changed 9 years ago by
| Milestone: | 1.4.4 → 1.4.5 |
|---|
Retargeting due to severity of regressions in 1.4.3.
comment:5 Changed 9 years ago by
| Milestone: | 1.4.5 → 1.4.4 |
|---|
Retargeting for 1.4.4 as per John’s request.
comment:6 Changed 9 years ago by
| Owner: | set to dmethvin |
|---|---|
| Status: | open → assigned |
comment:7 Changed 8 years ago by
| Owner: | dmethvin deleted |
|---|---|
| Status: | assigned → 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:9 Changed 8 years ago by
| Resolution: | → patchwelcome |
|---|---|
| Status: | open → closed |
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 8 years ago by
| Version: | 1.4.2 → 1.5 |
|---|
There wasn't a 1.4.5 release, was actually 1.5.
comment:11 Changed 8 years ago by
| Milestone: | 1.4.5 → 1.5 |
|---|
There was no 1.4.5 release, was actually 1.5.
Bad milestone. There is no edit option?