stapp Posted June 26, 2020 Report Share Posted June 26, 2020 Win 10 2004 updated to new beta via manual updates. All seems okay so far. So a2start will still show the 0..1..2..0..1 in task manager CPU details? It took a little while to start protection after update. Link to comment Share on other sites More sharing options...
Frank H Posted June 26, 2020 Report Share Posted June 26, 2020 24 minutes ago, stapp said: So a2start will still show the 0..1..2..0..1 in task manager CPU details? a2start CPU and RAM usage should be improved in beta 2020.7.0.10259, we're still on that. Link to comment Share on other sites More sharing options...
stapp Posted June 26, 2020 Author Report Share Posted June 26, 2020 4 minutes ago, Frank H said: a2start CPU and RAM usage should be improved in beta 2020.7.0.10259, we're still on that. I may need to restart machine as my a2start is usually quite low but it hasn't dropped much at all since I updated. Link to comment Share on other sites More sharing options...
stapp Posted June 26, 2020 Author Report Share Posted June 26, 2020 After a cold boot figures are more or less normal now although a2service is still a bit high ? Link to comment Share on other sites More sharing options...
stapp Posted June 26, 2020 Author Report Share Posted June 26, 2020 It must have needed a rest as it's all fine now Link to comment Share on other sites More sharing options...
JeremyNicoll Posted June 28, 2020 Report Share Posted June 28, 2020 I've waited a few days to see how 10259 seems to be behaving and it's certainly looking a lot better - cpu has stayed low. However I just got to teh end of a custom scan - which was long running - just over 4 hours; two drives (both SSDs, though one is fairly empty), 1.4 million files. The scan looked inside archives which is why it took so long (a scan of the same disks but skipping archives usually takes around 70-75 minutes). Also debug logging is on. But, see this summary from Process Hacker. A2start, during the scan had a WS of 1.1 GB, and still does now that the scan is finished. It peaked at 1.11 GB and peak virtual memory use was 1.41 GB. It's a hell of a lot for a process that's supposedly only doing the user-facing stuff. When I was watching the scan running, near the end, a2service - the bit that as far as I know is actually doing the work - was using around 770 MB. I don't understand how a2start can be using more memory then the scanner itself. Link to comment Share on other sites More sharing options...
Frank H Posted June 30, 2020 Report Share Posted June 30, 2020 On 6/29/2020 at 12:32 AM, JeremyNicoll said: But, see this summary from Process Hacker. A2start, during the scan had a WS of 1.1 GB, and still does now that the scan is finished. It peaked at 1.11 GB and peak virtual memory use was 1.41 GB. It's a hell of a lot for a process that's supposedly only doing the user-facing stuff. When I was watching the scan running, near the end, a2service - the bit that as far as I know is actually doing the work - was using around 770 MB. I don't understand how a2start can be using more memory then the scanner itself. Thanks for your feedback. We are investigating this already. Link to comment Share on other sites More sharing options...
Frank H Posted July 2, 2020 Report Share Posted July 2, 2020 we've fixed a memory leak in 2020.7.0.10272, which resolves the high ram use after a couple of custom scans- Link to comment Share on other sites More sharing options...
Recommended Posts