Hi,
The error happens for any file in a "massive" scan.
This is part of the log scanning
of the folder: C:\Program Files (x86):
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow\x64\TE.ProcessHost.Managed.Clr20.exe: OK
C:\Program Files (x86)\Windows Kits\10\Testing\Runtimes\TAEF\x86\MinTe\TE.ProcessHost.exe: Can't allocate memory ERROR
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow\TE.ProcessHost.Managed.exe: OK
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow\TE.ProcessHost.Managed.Clr20.exe: OK
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow\x64\TE.ProcessHost.Managed.exe: OK
C:\Program Files (x86)\Windows Kits\10\Testing\Runtimes\TAEF\MinTe\TE.ProcessHost.UAP.exe: Can't allocate memory ERROR
C:\Program Files (x86)\Windows Kits\10\Testing\Runtimes\TAEF\TE.ProcessHost.UAP.exe: Can't allocate memory ERROR
C:\Program Files (x86)\Windows Kits\10\Testing\Runtimes\TAEF\arm64\MinTe\TE.ProcessHost.UAP.exe: Can't allocate memory ERROR
C:\Program Files (x86)\Windows Kits\10\Testing\Runtimes\TAEF\x64\MinTe\TE.ProcessHost.UAP.exe: Can't allocate memory ERROR
C:\Program Files (x86)\Windows Kits\10\Testing\Runtimes\TAEF\x86\TE.ProcessHost.UAP.exe: Can't allocate memory ERROR
C:\Program Files (x86)\Windows Kits\10\Testing\Runtimes\TAEF\x86\MinTe\TE.ProcessHost.UAP.exe: Can't allocate memory ERROR
C:\Program Files (x86)\Windows Kits\10\Testing\Runtimes\TAEF\arm\MinTe\TE.ProcessHost.UAP.exe: Can't allocate memory ERROR
C:\Program Files (x86)\Windows Kits\10\Testing\Runtimes\TAEF\x64\TE.ProcessHost.UAP.exe: Can't allocate memory ERROR
C:\Program Files (x86)\TeamViewer\TeamViewer_Note.exe: Can't allocate memory ERROR
C:\OrCAD\OrCAD_10.5\tools\pcb\bin\techfile13.exe: Can't allocate memory ERROR
C:\OrCAD\OrCAD_10.5\tools\pcb\bin\techfile14.exe: Can't allocate memory ERROR
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\usr\bin\test.exe: Can't allocate memory ERROR
C:\Program Files\Git\usr\bin\tee.exe: Can't allocate memory ERROR
C:\Program Files\Common Files\microsoft shared\Team Foundation Server\12.0\LabManagement\TestAgentInstaller.exe: OK
C:\Program Files\Git\usr\bin\test.exe: Can't allocate memory ERROR
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\TestAgentConfig.exe: OK
C:\Program Files\dotnet\sdk\2.1.526\TestHost\testhost.exe: Can't allocate memory ERROR
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules\TShell\TShell\TaskActionHandlers\TestMetadataTool.exe: OK
An individual scan of any of these files runs ok.
I copied one of this files to a "testfolder" folder and started a scan, and everything goes ok:
Listening daemon: PID: 20796
MaxQueue set to: 512
C:\testfolder\TE.ProcessHost.exe: OK
The same happens for any scan of a folder:
LibClamAV Error: cli_calloc(): Can't allocate memory (65025792 bytes).
LibClamAV Error: cli_ac_init: Can't allocate memory for data->lsigcnt[0]
C:\inetpub\wwwroot\license\bin\License Generator.dll: Can't allocate memory ERROR
calloc_problem: Not enough space
LibClamAV Error: cli_calloc(): Can't allocate memory (65025792 bytes).
LibClamAV Error: cli_ac_init: Can't allocate memory for data->lsigcnt[0]
C:\inetpub\wwwroot\license\bin\log4net.dll: Can't allocate memory ERROR
calloc_problem: Not enough space
LibClamAV Error: cli_calloc(): Can't allocate memory (65025792 bytes).
LibClamAV Error: cli_ac_init: Can't allocate memory for data->lsigcnt[0]
C:\inetpub\wwwroot\license\bin\MiToken.ActiveDirectory.Library.dll: Can't allocate memory ERROR
C:\inetpub\wwwroot\license\bin\!!License Generator.dll.config: OK
In other tests, a scanning of my own folder (c:\users\jorge) suddenly stops:
C:\Users\jorge\OneDrive\20180302_095721.jpg: OK
C:\Users\jorge\Pictures\Cumple\Cumple\DSCN1170.JPG: OK
C:\Users\jorge\OneDrive\20180302_095738.jpg: OK
memory allocation of 47775744 bytes failed
...and clamd stops.
I'm testing using clamd -F command, not running as a service, just to get the log dump in the console screen.
The connection is performed from my own application and the command sent to the clamd socket is:
nMULTISCAN
C:\Program Files (x86)\n
or
nMULTISCAN c:\users\jorge\n
The machine I'm using for testing has 32GBytes, and only 29% is in use.
Clamav uses 1GB.
Thank you
Jorge