Hi folks,
For some reason I haven't been able to find a good answer via googling on this.
I've got an niche application that has a memory leak. I'm working with the developer to track down what's going on. It only leaks "sometimes" and "for some people." Developer believes it's a driver problem on my side (I'm running a plain vanilla computer running only windows 10 and this application, nothing else).
So I have wanted to log and graph memory usage by this application's process over time (measured in hours/days/week scales), measuring it by the minute as part of my reporting into the dev.
It has been a long time (over a decade) since I've had to do anything like this but I fired up Performance Monitor and with a bit of googling was able to set up a data collector for the relevant process' "private bytes," and get it to the point where it shows it was collecting data.
Here's my problem and the question: I am unable to see the data graphs (or access the relevant log file) while the data is collecting. I have to stop the collector to be able to access the file/graph. Is this normal? I could swear back in the day I could watch this in real time and just leave the graph up; it would show new data and either compress the graph timescale as collection went on or would scroll the graph. But I'm completely unable to interact with the data while it is collecting.
Am I doing something wrong, or is this just how the tool works? Perhaps I was using a different tool. I'm assuming I'm in "user error" territory on this but surprised that in a bit of searching online I don't see this reported as a problem.
Your input would be appreciated. Thanks!
For some reason I haven't been able to find a good answer via googling on this.
I've got an niche application that has a memory leak. I'm working with the developer to track down what's going on. It only leaks "sometimes" and "for some people." Developer believes it's a driver problem on my side (I'm running a plain vanilla computer running only windows 10 and this application, nothing else).
So I have wanted to log and graph memory usage by this application's process over time (measured in hours/days/week scales), measuring it by the minute as part of my reporting into the dev.
It has been a long time (over a decade) since I've had to do anything like this but I fired up Performance Monitor and with a bit of googling was able to set up a data collector for the relevant process' "private bytes," and get it to the point where it shows it was collecting data.
Here's my problem and the question: I am unable to see the data graphs (or access the relevant log file) while the data is collecting. I have to stop the collector to be able to access the file/graph. Is this normal? I could swear back in the day I could watch this in real time and just leave the graph up; it would show new data and either compress the graph timescale as collection went on or would scroll the graph. But I'm completely unable to interact with the data while it is collecting.
Am I doing something wrong, or is this just how the tool works? Perhaps I was using a different tool. I'm assuming I'm in "user error" territory on this but surprised that in a bit of searching online I don't see this reported as a problem.
Your input would be appreciated. Thanks!