B
Brian R
I have a memory leak in a program we have developed in-house. This leak
eventually [after 20+ hours of running] causes the program to lockup on a
frame grabber function. The PC had 512M of RAM and I setup virtual memory to
be 4G. When the program locks up, Task Manager shows PF usage of around 1.3GB.
Looking for a quick solution, I upgraded to 2G of RAM and left the virtual
memory setting at 4G however this did not change the situation. When the
program locks up, Task Manager still shows PF usage of 1.3GB.
As an experiment, I opened up multiple instances of Internet Explorer with
very large XML files. This allowed me to get the PF usage beyond 1.3 GB. I
then would run the portion of the program that calls the frame grabber
function that normally locks up but it did not lock up. In fact it didn't
lock up until I approched the maximum 4GB. Thus I am wondering if Windows has
a per application memory limit and, if so, is there a way to increase this
limit?
eventually [after 20+ hours of running] causes the program to lockup on a
frame grabber function. The PC had 512M of RAM and I setup virtual memory to
be 4G. When the program locks up, Task Manager shows PF usage of around 1.3GB.
Looking for a quick solution, I upgraded to 2G of RAM and left the virtual
memory setting at 4G however this did not change the situation. When the
program locks up, Task Manager still shows PF usage of 1.3GB.
As an experiment, I opened up multiple instances of Internet Explorer with
very large XML files. This allowed me to get the PF usage beyond 1.3 GB. I
then would run the portion of the program that calls the frame grabber
function that normally locks up but it did not lock up. In fact it didn't
lock up until I approched the maximum 4GB. Thus I am wondering if Windows has
a per application memory limit and, if so, is there a way to increase this
limit?