FIX: JScript leaks memory when an application repeatedly creates and destroys threads (831191)


The information in this article applies to:

  • Microsoft JScript 5.6
  • Microsoft Windows Server 2003, Standard Edition
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Datacenter Edition
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Server 2003, 64-Bit Enterprise Edition
  • Microsoft Windows Server 2003, 64-Bit Datacenter Edition
  • Microsoft Windows XP Professional
  • Microsoft Windows XP Home Edition
  • Microsoft Windows XP 64-Bit Edition Version 2002
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional

SYMPTOMS

If you use the Microsoft JScript engine on a thread and the thread is destroyed, approximately 150 bytes of heap memory are leaked. Typically, this behavior does not cause a problem. However, if an application repeatedly creates and destroys threads many times, and if the application uses JScript on those threads, the memory usage increase may be sufficient to decrease the performance of the system.

RESOLUTION

Software update information

A supported software update is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This software update may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next service pack that contains this software update.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the software update. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have Microsoft JScript 5.6 installed on the system before you apply this software update. Microsoft JScript 5.1 is not affected by this problem and does not require this software update.

Restart requirement

You do not have to restart your computer after you apply this software update if the JScript.dll file is not in use when you apply this software update.

Software update replacement Information

This software update does not replace any other software updates.

File information

The English version of this software update has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version     Size    File name
   ----------------------------------------------------
   18-Nov-2003  16:25  5.6.0.8820  446,464  Jscript.dll

WORKAROUND

To work around this problem, do not create and destroy large numbers of threads. When you use thread pools (when you reuse existing threads) you use the operating system more efficiently.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

Microsoft is researching this problem and will post more information in this article when the information becomes available.

MORE INFORMATION

When you monitor the memory usage of an application, monitor both the Private Bytes and Virtual Bytes counters of the Process object in Performance Monitor. The memory that an application uses may increase and decrease significantly while the application runs. Valid reasons may exist that cause the memory that an application uses to increase over time.

To make sure that the problem that this article describes is causing a specific memory leak, you must repeat the suspected operation (in this case, creating a thread, using JScript on the thread, and then destroying the thread again) many thousands of times to determine whether the memory usage fluctuations are the program's typical behavior.

For additional information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Modification Type:MinorLast Reviewed:10/25/2005
Keywords:kbHotfixServer kbQFE kbbug kbQFE kbfix KB831191 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.