FIX: Resource Leak with READ TIMEOUT VALID Command

 Last reviewed: September 22, 1997
Article ID: Q123354 
2.60a   | 2.60a  | 2.60a     | 2.60
WINDOWS | MS-DOS | MACINTOSH | UNIX kbenv kbprg kbfixlist kbbuglist

The information in this article applies to:

  • Microsoft FoxPro for Windows, version 2.6a
  • Microsoft FoxPro for MS-DOS, version 2.6a
  • Microsoft FoxPro for Macintosh, version 2.6a
  • Microsoft FoxPro for UNIX, version 2.6

SYMPTOMS

The amount of memory that FoxPro is using will increase each time the command READ TIMEOUT VALID is issued. This occurs only when both the TIMEOUT and the VALID clauses are used with the READ command.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem was corrected in Visual FoxPro 3.0 for Windows.

MORE INFORMATION

Steps to Reproduce Problem

  1. Enter the following code in a program file:

    DO WHILE LASTKEY()!=27 

          READ TIMEOUT .25 VALID .T.
      ?SYS(1016)
    ENDDO

  2. Run the program. The amount of memory being used, as returned by the SYS(1016) command, will increase with each loop until you press the ESCAPE key to end the program.

Additional reference words: FoxWin FoxDos FoxMac FoxUnix 2.60 2.60a
fixlist3.00 buglist2.60 buglist2.60a VFoxWin
KBCategory: kbenv kbprg kbfixlist kbbuglist
KBSubcategory: FxenvMemory
Keywords : FxenvMemory kbbuglist kbenv kbfixlist kbprg
Version : 2.60a | 2.60a | 2.60a | 2
Platform : MACINTOSH MS-DOS UNIX WINDOWS
Solution Type : kbfix

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 22, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.