If your computer or server has a very high memory usage, we will need to inspect the amount of Private Bytes and Virtual Bytes that are currently being used by a CentreStack component to determine if there is a memory leak in a particular software component.
Private Bytes is an estimate of the amount of memory (non-paged and paged) that a software component is using and it should be a stable number. A Private Bytes that keeps growing endlessly or that uses a high percentage of the total available memory of the computer could indicate a memory leak.
Virtual Bytes is an estimate that includes the Private Bytes plus memory-mapped files, plus bytes that are awaiting to be re-allocated by a run-time environment's memory manager (standby list). Like Private Bytes, this number should also be stable and should not consume a high percentage of the total available memory.
The most accurate way to investigate these numbers on Windows Systems is to use the Windows Performance Monitor (perfmon). Here are the steps:
Step 1 - Open your Windows Task Manager and inspect the Details page sorted from highest to lowest Memory usage. For the rest of this example, we are going to assume that the Windows Client process is using a lot of RAM on an end-user's workstation. The Windows Client and the Server Agent's main process is called CoDesktopClient.exe.
If you are having memory issues on the CentreStack server instead, some of the possible processes that you may want to investigate belong to the following IIS application pools:
- Namespace (w3wp.exe) - The process responsible for user actions, permission checks, etc.
- UploadDownloadProxy (w3wp.exe) - The process responsible for file syncing operations.
- Management (w3wp.exe) - The process responsible for most of the Cluster and Tenant Dashboard pages.
- Portal (w3wp.exe) - The process responsible for most of the File Browser and other end-user pages.
- GladinetCloudMonitor.exe (w3wp.exe) - The process responsible for scheduling, CentreStack settings caching, reporting, etc.
Step 2 - Open a Windows Run box by pressing the Windows Key + R.
Step 3 - Type "perfmon" without quotes and press the OK button.
Step 4 -Click on the green plus-sign to add new performance counters.
Step 5 - Add new counters for <Local computer>, then select Process and then the CoDesktopClient process that had the highest memory usage in Task Manager (you may have more than one of these processes running).
Step 6 - Right-click on the bottom area and choose Properties...
Step 7 - Remove all Counters except Virtual Bytes and Private Bytes.
Step 8 - Hit the OK button to apply the filters.
Step 9 - Click on the view drop-down menu and choose Report.
Step 10 - Right-click on an empty area of the Report and Save Image As...
Step 11 - Send the image to email@example.com along with the product version.
Article is closed for comments.