There is a major problem with the latest stable build (40412) which can be demonstrated by creating an empty website and simply dropping a script manager on a page. When refreshing this page repeatedly in IE6, the browser's memory footprint goes through the roof - 5MB IE memory increase each page refresh. This was not a problem with the 30512 build. Can this problem be resolved? We have developed new features in a number of apps using the latest build and will otherwise need to back out and rewrite these features using alternative tools.
The above issue is not present when running IE8 on the client but we cannot force our large corporate customer (3000+ desktops) to move from IE6 whilst it is still supported by Microsoft in line with XP support. As this problem appears to have been introduced in the latest version, it should not be too difficult to isolate and resolve.
==============
Repro steps:
1. Get a Win 2K3 machine. Install .Net framework 3.5 SP1 and 4.0 RTM.
2. Deploy the attached web app in IIS. Make sure it is run on 4.0 framework.
(The page only has one control, that is “ScriptManager”. And nothing else is related to ACT.)
(In the bin folder, there’s an ACT assembly build 4.0.40412.2)
3. Browse “IE6 Memory Leak.aspx” with IE6. Open “Task Manager”, and monitor the process “iexplorer.exe”.
4. Refresh the page for many times. See the memory-use of process “iexplorer.exe”.
Expect:
Memory-use will not increase evidently while you’re refreshing the page.
Actual:
Memory-use will increase evidently by each refresh.
And will not stop at a limit.
Here’re the repro/not-repro conditions:
1. Repro on IE6 or IE7. Not repro on IE 8.
2. Repro when the page get a “ScriptManager”, and bin folder get ACT build 4.0.40412.2.
Not repro with ACT build 3.5.40412, or when you have removed ACT from bin.
3. Also repro on Cassini server.
So I think it is a bug of ACT build 4.0.40412.2. But notice this, it is not repro on 3.5.40412.2.
Comments: It seems that this error is caused by ToolkitScriptManager. Starting with the v15.1 release, we have removed it. So now, this problem is resolved.
The above issue is not present when running IE8 on the client but we cannot force our large corporate customer (3000+ desktops) to move from IE6 whilst it is still supported by Microsoft in line with XP support. As this problem appears to have been introduced in the latest version, it should not be too difficult to isolate and resolve.
==============
Repro steps:
1. Get a Win 2K3 machine. Install .Net framework 3.5 SP1 and 4.0 RTM.
2. Deploy the attached web app in IIS. Make sure it is run on 4.0 framework.
(The page only has one control, that is “ScriptManager”. And nothing else is related to ACT.)
(In the bin folder, there’s an ACT assembly build 4.0.40412.2)
3. Browse “IE6 Memory Leak.aspx” with IE6. Open “Task Manager”, and monitor the process “iexplorer.exe”.
4. Refresh the page for many times. See the memory-use of process “iexplorer.exe”.
Expect:
Memory-use will not increase evidently while you’re refreshing the page.
Actual:
Memory-use will increase evidently by each refresh.
And will not stop at a limit.
Here’re the repro/not-repro conditions:
1. Repro on IE6 or IE7. Not repro on IE 8.
2. Repro when the page get a “ScriptManager”, and bin folder get ACT build 4.0.40412.2.
Not repro with ACT build 3.5.40412, or when you have removed ACT from bin.
3. Also repro on Cassini server.
So I think it is a bug of ACT build 4.0.40412.2. But notice this, it is not repro on 3.5.40412.2.
Comments: It seems that this error is caused by ToolkitScriptManager. Starting with the v15.1 release, we have removed it. So now, this problem is resolved.