If you suspect a memory leak in the program
ZennoPoster is a complex program with a huge number of functions and thousands of use cases. We try to test most of them, but 100% is not easy to achieve. If you have a situation that the program starts to slow down after a while, a detailed report on the erroneous behavior of the program in your personal case will help us a lot. This information will help the development team troubleshoot the cause of the error.
Links to software used in the article
Process Explorer
Algorithm for recording a memory leak (by the example of ZennoPoster)
It is necessary to check which of the processes is leaking memory, for example, it is convenient to look through Process Explorer in a tree-like form. There are two ZennoPoster processes in ZP7, distinguished by the -ZennoPosterCore argument.
You need to start dotMemory, start ZennoPoster, in dotMemory do Attach to the process with the -ZennoPosterCore parameter if the Core process is eating memory or without this argument if the UI process.
dotMemory will connect, you need to make several snapshots using the Get Snapshot button: at the beginning of work, when memory starts leaking, when there is a lot of memory leaks.
After receiving these three snapshots, you need to do a Detach or Kill Process.
Next, click on the top left on Home, go to Workspaces, the top workspace must be current, you can check by date.
Click on the Export button near the current workspace and send it to us.