Bug: maxed-out resources in virtual memory

Alexander Wiedenbruch 0 Reputation points
2024-09-02T14:08:41.4+00:00

We experience maxed-out resources in virtual memory when running tests with SmartBear TestExecute for longer period of times (For example, a few or several dozen hours)

The issue was identified as a potential kernel memory leak, particularly with the Windows service RPCSS, observed during a session with the customer using Windows 10 on desktop builds.

We also think that places where we’re leaking some memory is MmSt - this is for I/O caching/memory mapping.

The issue was observed on Windows 10 desktop builds, not server builds, with suspicions of a kernel memory leak, particularly involving the Windows service RPCSS and memory mapping (MmSt)

Various tools and methods were suggested for further investigation, including Process Explorer, VMMap, and PoolMon, to monitor memory consumption and potential leaks.

As described above it looks like a leak in windows memory.

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Jacen Wang 980 Reputation points Microsoft External Staff
    2024-09-08T15:34:44.9966667+00:00

    Hello,

    For memory leaks, it is advised to make sure your Windows 10 and all relevant drivers are up to date first. And check for SmartBear TestExecut version updates.

    If possible, try to reproduce the problem in a controlled environment where you can systematically enable/disable services or applications to identify any potential conflicts or triggers. At the same time, use Windows performance toolkits, such as Windows Performance Recorder, to provide in-depth performance and memory usage tracking over time.

    Windows Performance Recorder | Microsoft Learn

    Try enabling a driver verifier to stress test your drivers and catch any drivers that are behaving abnormally.

    Caution

    • Running Driver Verifier could cause the computer to crash.

    • You should only run Driver Verifier on computers that you are using for testing and debugging.

    • You must be in the Administrators group on the computer to use Driver Verifier.

    Driver Verifier - Windows drivers | Microsoft Learn

    In addition, it is recommended that you contact SmartBear's support team and provide the details you have collected. They may offer additional insights or suggestions based on your findings and their experience with similar issues. Best regards

    Jacen

    ——————————————————————————————————

    If the Answer is helpful, please click "Accept Answer" and upvote it.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.