Opened 10 years ago
Closed 9 years ago
#12153 closed defect (wontfix)
IE6 - continuous memory increase when repeating connecting/disconnecting events
Reported by: | Evan | Owned by: | Kris Zyp |
---|---|---|---|
Priority: | blocker | Milestone: | tbd |
Component: | Events | Version: | 1.5 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
Met with this issue when dealing with #12037
- There are continuous memory increase if we repeat connecting/disconnecting events in IE6.
We can reproduce the issue with the attached "test_connect_leak.html"
- When running with sIEve on IE6, memory increases from 9498k to 13348k in 10 mins(more increase if kept running)
This issue is only observable in IE6, not sure if it's due to flawed GC way of IE6.
Attachments (1)
Change History (6)
Changed 10 years ago by
Attachment: | test_connect_leak.html added |
---|
comment:1 Changed 10 years ago by
severity: | critical → normal |
---|
comment:3 Changed 9 years ago by
Owner: | changed from sjmiles to Kris Zyp |
---|---|
Reporter: | changed from evan to Evan |
Status: | new → assigned |
I looked at memory leaks with Kris with the new event code. He got it down to performing comparably to the old code, but not better, so probably this problem still exists.
I think though at this point we want to close this as wontfix. I'll let Kris do that if he agrees.
I don't know why csnover set priority to blocker on a ticket from 1.5.
comment:4 Changed 9 years ago by
Priorities were changed from highest/high/normal/low/lowest (or something like that) to blocker/high/low because so much granularity was worthless. Since nobody ever used the “highest” priority, all tickets that were “high” before were changed to “blocker” in a bulk change (there were not many “high” priority tickets, either, but this was one of them).
comment:5 Changed 9 years ago by
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
With the decreased market share of old IE browsers, and the complexity of trying to fix this, I don't think it is worth extra code size and maintenance overhead.
Changing severity to normal since this is only observed in IE6