Microsoft KB Archive/174244: Difference between revisions
(importing KB archive) |
m (Text replacement - """ to """) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 45: | Line 45: | ||
== SYMPTOMS == | == SYMPTOMS == | ||
Repeatedly calling the SAVE SCREEN TO | Repeatedly calling the SAVE SCREEN TO <memvar> and RESTORE SCREEN FROM <memvar> commands causes the operating system to run low on memory.<br /> | ||
<br /> | <br /> | ||
In Windows NT 4.0, the following message appears in a window titled | In Windows NT 4.0, the following message appears in a window titled "System Process-Out of Virtual Memory": | ||
<div class="errormessage"> | <div class="errormessage"> | ||
Latest revision as of 11:07, 21 July 2020
Article ID: 174244
Article Last Modified on 8/12/1999
APPLIES TO
- Microsoft Visual FoxPro 5.0 Standard Edition
- Microsoft Visual FoxPro 5.0a
This article was previously published under Q174244
SYMPTOMS
Repeatedly calling the SAVE SCREEN TO <memvar> and RESTORE SCREEN FROM <memvar> commands causes the operating system to run low on memory.
In Windows NT 4.0, the following message appears in a window titled "System Process-Out of Virtual Memory":
After clicking OK, the following error message appears:
In Windows 95, the following error appears:
RESOLUTION
As a workaround, place the following two commands before the RESTORE SCREEN FROM command in the code example below:
ACTIVATE SCREEN CLEAR
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been fixed in Visual Studio 97 Service Pack 3.
For more information, please see the following article in the Microsoft Knowledge Base:
170365 INFO: Visual Studio 97 Service Packs - What, Where, and Why
MORE INFORMATION
The amount of the memory leak with each iteration of the SAVE and RESTORE combination is dependent on screen resolution, size of Visual FoxPro desktop, and color depth. Memory leakage will be some multiple of the product of the _SCREEN.Width and _SCREEN.Height. This can be on a magnitude of megabytes per iteration.
Steps to Reproduce Behavior
WARNING: Running this code causes a low memory situation on the computer. This condition may cause the operating system to become unstable. Close all running applications and save your data before following this procedure. To close all open applications, press CTRL+ALT+Delete to open the NT Task Manager or the Windows 95 Close Program window, and then close all the other applications you have running.
Create a program containing the following code:
ON KEY LABEL f12 CANCEL SAVE SCREEN TO s_var Y=1 DO WHILE .T. Y=Y+1 @ 1,1 SAY Y RESTORE SCREEN FROM s_var ENDDO
- Run the program.
The error message may take several minutes to appear depending on the amount of physical memory and the hard drive space available for the swap file.
Additional query words: memory leak restore from
Keywords: kberrmsg kbbug kbfix kbvs97sp2fix KB174244