MeshCentral/MeshAgent
1
0
Fork 0
mirror of https://github.com/Ylianst/MeshAgent synced 2025-12-15 15:53:55 +00:00
Code Issues Releases Wiki Activity

Added documentation describing leaktest.js which was used to find memory and handle leaks.

Browse Source
This commit is contained in:
Bryan Roe
2022-08-15 10:20:11 -07:00
parent 5210639d8f
commit 87dbd0d5ac
2 changed files with 300 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/testing/ReleaseCheckList.md
View File

@@ -81,4 +81,15 @@ service restart
Using the meshcmd that we built previously, we can manually run some AMT tests on AMT capable platforms.
1. `meshcmd AmtInfo`. This will test mei functionality, and let you know the provisioning state of AMT.
2. `meshcmd AmtEventLog`. If you run this on an already provisioned AMT, it will test the WSMAN functionality to retrieve the AMT event log.
2. `meshcmd AmtEventLog`. If you run this on an already provisioned AMT, it will test the WSMAN functionality to retrieve the AMT event log.
### Manual Leak Tests
The leaktest.js can be run with the agent, using Visual Studio or Valgrind, to aid in testing for memory leaks. For windows, simply load the solution in Visual Studio, and run the MeshService project in the debugger, with the following cmdline options:
```bash
..\test\leaktest.js
```
For Linux, run Valgrind with the agent, in the following way:
```bash
valgrind ./meshagent_x86-64 test/leaktest.js_
```