Memory Leak?

[tletter]

After completing Sharing a VSP project, I started a new project. However as can be seen in Task Manager, the VS memory utilization is still stuck at 6,041MB. The only way to release this memory is to close VS. Why would VS holding on to this memory if not for a memory leak?

[aljimenez]

Maybe this indicates a memory leak, maybe not. Programs could hold buffers used in the prior project and re-use for the next project since freeing memory and reallocating is expensive, for example.

[tletter]

Programs could hold buffers used in the prior project and re-use for the next project

The problem is that when another project is opened, the memory utilization increases from the previous level that VS had used, e.g. 6,041MB, and soon Windows reports "Your computer is low on memory". There is no recovery other than shutting down VS.

[aljimenez]

This may still not be considered a bug. The new project may be very different than the previous one, and this may result in inefficient use of old allocated memory. I don't think we would get any priority chasing this issue as a bug, so I recommend a VS restart, especially after a complex project is finished. I think if you do several projects in a row that are not too complex and they are similar it will probably work OK without restarting VS.

[Ken Berry]

The other thing that potentially implies a bug would be that others are reporting the same thing -- especially if their computers are telling them they are out of memory. So far you seem to be the only one with this problem...