Resolving high memory usage
If you experience error messages related to high memory usage, the following includes instructions for resolving this issue. If you still encounter issues, please contact us at [email protected].
For Windows
Check Central Processing Unit (CPU) usage
Step 1: Check to see if there are any applications that are currently open and associated with a high CPU usage. Temporarily close those applications.
Step 2: Open the Task Manager to see if there are any chromedriver.exe sessions running in the background. Select and end unnecessary sessions.
Clear temporary files
Step 3: The following includes instructions for cleaning up cached and temporary files. The following instructions will clear all temporary files on your machine.
To clear temporary files on a Windows machine:
- First close Provar
- Select Run from the Start Menu
- Type %temp% in the Run field and click Enter
- Delete the temporary files
For Mac
Check Central Processing Unit (CPU) usage
Step 1: Check to see if there are any applications that are currently open and associated with a high CPU usage. Temporarily close those applications.
Step 2: Open the Activity Monitor to see if there are any chromedriver.exe sessions running in the background. Select and end unnecessary sessions.
Clear temporary files
Step 3: The following includes instructions for cleaning up cached and temporary files.
- First close Provar
- In the Finder menu, choose Go to Folder or use Shift + CMD + G
- In the Go To Folder dialog box enter ~/Library/Caches
- Select all of the files in the Cache folder
- Once you have all the files selected, you can delete them by dragging them to the Trash folder
Refresh metadata
Step 4: You can refer to this help page for step-by-step instructions.
Connection issues
Step 5: Navigate to the Problems tab in Provar and check to see if you find any connection-related error messages.
Step 6: If you have a connection associated with a large volume of metadata, it may be interfering with other Provar connections. Select the connection and temporarily disable test validation by adding the following entry in the provar.ini file:
-Dcom.provar.validation.disable=true
Note: You may need to add permissions before editing the provar.ini file. You can refer to this support article to learn more.
Increase memory in the provar.ini file
Step 7: 1024 megabytes of system memory is assigned by default in Provar. If you want to change the memory allocation, you can refer to this support article to increase system memory.
If you follow the instructions listed above and are still experiencing issues, please visit the Provar Success Portal to raise a case. Please include the following information:
- A description of the issues you are experiencing
- Logs from your Workspace
- Screenshots of error messages
- Your system details (e.g. operating system, RAM specifications, disk space, processor specifications)
- General information
- Licensing Provar
- Provar trial guide and extensions
- Using Provar
- API testing
- Behavior-driven development
- Creating and importing projects
- Creating test cases
- Custom table mapping
- Functions
- Debugging tests
- Defining a namespace prefix on a connection
- Defining proxy settings
- Environment management
- Exporting test cases into a PDF
- Exporting test projects
- Override auto-retry for Test Step
- Managing test steps
- Namespace org testing
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- Reload Org Cache
- Reporting
- Running tests
- Searching Provar with find usages
- Secrets management and encryption
- Setup and teardown test cases
- Tags and Service Level Agreements (SLAs)
- Test cycles
- Test plans
- Testing browser options
- Tooltip testing
- Using the Test Palette
- Using custom APIs
- Callable tests
- Data-driven testing
- Page objects
- Block locator strategies
- Introduction to XPaths
- Creating an XPath
- JavaScript locator support
- Label locator strategies
- Maintaining page objects
- Mapping non-Salesforce fields
- Page object operations
- ProvarX™
- Refresh and reselect field locators in Test Builder
- Using Java method annotations for custom objects
- Applications testing
- DevOps
- Introduction to test scheduling
- Apache Ant
- Configuration for Sending Emails via the Provar Command Line Interface
- Continuous integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Provar secrets password in Microsoft Azure Pipelines
- Parallel Execution in Microsoft Azure Pipelines Using Multiple build.xml Files
- Parallel Execution in Microsoft Azure Pipelines using Targets
- Parallel execution in Microsoft Azure Pipelines using Test Plans
- Bitbucket Pipelines
- CircleCI
- Copado
- Docker
- Flosum
- Gearset DevOps CI/CD
- GitHub Actions
- Integrating GitHub Actions CI to Run Provar CI Task
- Remote Trigger in GitHub Actions
- Parameterization using Environment Variables in GitHub Actions
- Parallel Execution in GitHub Actions using Multiple build.xml Files
- Parallel Execution in GitHub Actions using Targets
- Parallel Execution in GitHub Actions using Test Plan
- Parallel Execution in GitHub Actions using Job Matrix
- GitLab Continuous Integration
- Travis CI
- Jenkins
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Reporting
- Salesforce DX
- Git
- Team foundation server
- Version control
- Salesforce testing
- Adding a Salesforce connection
- Assert Page Error Messages on Add/Edit Product
- Dynamic Forms
- Internationalization support
- List and table testing
- Salesforce Release Updates
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) locator support
- Salesforce console testing
- Visualforce Testing
- Performance Best Practices
- Testing best practices
- Troubleshooting
- Browsers
- Configurations and permissions
- Connections
- DevOps
- Error messages
- Administrator has blocked access to client
- JavascriptException: Javascript error
- macOS Big Sur Upgrade
- Resolving failed to create ChromeDriver error
- Resolving Jenkins license missing error
- Resolving metadata timeout errors
- Test execution fails – Firefox not installed
- Update to Opportunity field validation behaviour
- Licensing, installation and firewalls
- Memory
- Test Builder and test cases
- Release notes