The memory is not being released as it is waiting for garbage collection to happen. Once the GC performs a collection the memory will be released. However as additional web pages are displayed the memory will raise again up to a certain size. The net result is that the process will appear to consume this cap memory size since the rending of the images is eating up the memory quickly.
The memory usage increases per page due to thumbnail.aspx being called multiple times with a single rendered page, i.e., 20 times if displaying 20 images per page. However garbage collection happens automatically when a certain amount of memory is used. One way you can reduce the memory held by the process is to force garbage collection after rending each page. A quick way to accomplish this is to add the following to the bottom of the default.aspx file:
<% System.GC.Collect(); %>
This will force garbage collection. And I will guess that with regard to your machine it will reduce the memory held by the process to approximately 55k.
Hope that helps.
-KIRBY
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I have 125 large images around 1.5 mb each.
when i test it with photoroom the process aspnet_wp.exe takes more than 100mb of RAM.
Even though my machine has 500mb ram after closing photoroom the the memory occupied by aspnet_wp.exe is not cleared. How to get over this?
Iam using Photoroom v1.5
TIA
Jayakamal
The memory is not being released as it is waiting for garbage collection to happen. Once the GC performs a collection the memory will be released. However as additional web pages are displayed the memory will raise again up to a certain size. The net result is that the process will appear to consume this cap memory size since the rending of the images is eating up the memory quickly.
The memory usage increases per page due to thumbnail.aspx being called multiple times with a single rendered page, i.e., 20 times if displaying 20 images per page. However garbage collection happens automatically when a certain amount of memory is used. One way you can reduce the memory held by the process is to force garbage collection after rending each page. A quick way to accomplish this is to add the following to the bottom of the default.aspx file:
<% System.GC.Collect(); %>
This will force garbage collection. And I will guess that with regard to your machine it will reduce the memory held by the process to approximately 55k.
Hope that helps.
-KIRBY
This should be fixed in cvs as of yesterday.