I'm trying to capture 1000,000 data continuously with capture function of PicoScope6.(Tool>Alarm>Capture)
But it absolutely downs at around the number of 1,187 without any error and alarm message.
(The number seems no relation with the data size and capture frequency)
Condition:
Model:PicoScope4424
Number of Channel:3(A,B,C)
Range:+-10V,50ms/div,1kS
Trigger:Continuous,Channel A
PC:RAM4.0GB,Processor1.7GHz,HDD20GB(Free space)
OS:Windows 7
I have managed to run your psdata file, having modified the save file location and removed the trigger, and it falls over at the same point for me. I have passed the information onto our development team and will report back when I have an answer.
Sorry for not replying. The developers have found a memory leak in the code related to the saving of multiple files and this has now been fixed although is not yet in a released version. This should be available soon once further testing has been completed.
Hi
I'm using Picoscope 6.6.46.1 with the alarm/save on trigger feature. I get around 1190 files, then no more and Picoscope closes. So it sounds like the same problem. Is there a version with a fix for this problem?
Hi, I forgot to ask, can you tell me what type of memory leak? Ideally I'd use Performance Monitor to check that there is no leak now, so need your guidance on what memory parameters to watch. In my application I want to leave Picoscope running unattended for many weeks, so any memory leak will be a problem.
The leak was related to the drawing of traces, the memory wasn't being recovered if the data was automatically saved to file. It was being recovered if you just went on to drawing the next buffer without any save. You can clearly see the effect by looking at memory use with the Processes tab of Task Manager.