Opened 14 years ago

Closed 14 years ago

#4141 closed defect (fixed)

dojo.connect pseudo-leaks nodes (GC failure, not page refresh) on IE7

Reported by: sjmiles Owned by: sjmiles
Priority: high Milestone: 0.9
Component: Core Version: 0.9
Keywords: Cc:
Blocked By: Blocking:


IE7 will refuse to GC DOM nodes under some conditions, including:

  1. have any content and are not part of a document
  2. have any circular DOM/JS references, even if both ends of the cycle are reference-free

In general, getting a non-trivial DOM node to GC at all is difficult. You must use Dojo dojo._destroyElement or equivalent.

Nodes with DOM/JS circularity are problematic even under dojo._destroyElement, so we will have to employ the indirect-connect logic originally designed for IE6.

Change History (4)

comment:1 Changed 14 years ago by sjmiles

Owner: changed from anonymous to sjmiles

comment:2 Changed 14 years ago by sjmiles

Priority: normalhigh
Status: newassigned

comment:3 Changed 14 years ago by sjmiles

Milestone: 0.9

comment:4 Changed 14 years ago by sjmiles

Resolution: fixed
Status: assignedclosed

(In [10187])
Aggressive leak protection on IE7 (which is more broken than we had hoped), fixes #4141.

Indirect listener from disconnect package, fixes #4142.

Remove closure over 'node' in _fixCallback on IE, fixes #4159.

Key hack to normalize arrow and page keys on Safari for Windows, fixes #4129.

Note: See TracTickets for help on using tickets.