I recently submitted a bug report about an issue I was having where when downloading large files (250MB and 675MB) the memory usage on the ASP.NET worker process was increasing by the same size of the file, and that in some cases this memory never got freed up.  The files upload fine, and I have my web.config set to allow me to download files this large.  Essentially what happens is that when I start downloading the file, I can see the memory usage climb up in the task manager as the file is buffered.  By the time I get the dialog to open or save in the browser, the worker process is >800MB for the large file.  The next issue is that when I click 'Cancel' (looks like this is only in FireFox), the download is cancelled, but the memory used by the worker process never goes back down to normal.   I have the source code and uncommenting the line that flushes the response seems to solve the problem, but I imagine it was commented out for a reason.  Can you detail the implications of uncommenting that line, or provide other suggestions about my issue.

Thanks in advance
Bryan