ITsVISTA
Information that makes life easier when it comes to installing, managing, and using Windows Vista.
Start About FAQ Blogroll Shop

All tag results for ‘Leak’

KB958124

October 30th, 2008 · No Comments · 120 views

Consider the following scenario:

  • You set up a Windows Management Instrumentation (WMI) notification query to monitor event log changes on a Windows Server 2008-based or Windows Vista-based computer.
  • Some events are added that trigger the WMI notification query.

In this scenario, the memory usage of one instance of the wmiprvse.exe process increases quickly until the memory is exhausted.

KB951119

April 24th, 2008 · No Comments · 259 views

When you run an application that calls the MessageBeep function on a Windows Vista-based computer, several system page table entries (PTEs) are leaked. Under most circumstances, this minor leak is not noticeable. However, if the MessageBeep function is frequently or repeatedly called, this leak may cause the computer to stop responding (hang).

Note: You can view the system PTE usage in Performance Monitor. To do this, add the Free System Page Table Entries counter to Performance Monitor.

KB948572

April 18th, 2008 · No Comments · 175 views

Consider the following scenario:

  • In a network environment, you set up a Server Message Block (SMB) connection between two Windows Vista-based computers that use the SMB2 protocol.
  • The SMB session requires more than one roundtrip.
  • The connection is closed while Windows Vista is processing the response for the second roundtrip.

In this scenario, a handle leak may occur. Specifically, when you run the Net Session command, invalid session information is returned. This session information may indicate in the Opens column that this session has an invalid count.

After the issue occurs, you must restart the SMB service or the computer that is running this service.

Note: This issue also occurs in Windows Server 2008.

KB949700

April 3rd, 2008 · No Comments · 576 views

On a Windows Vista-based computer, when you run an application that uses the Refresh method of the IWbemRefresher interface, the application may result in a memory leak.

After the application runs for several days, the computer may become unresponsive. In this case, you have to restart the computer.

Additionally, if you use system performance monitor tool (perfmon.exe) to monitor the Private Bytes counter of the application, you may notice that the private bytes increase quickly.