Open jtabox opened 3 weeks ago
Hi,
When I run clamscan.exe (I don't have the daemon running) it spams the terminal (20-30 lines) with the following:
clamscan.exe
LibClamAV Error: sigperf_events_init: events table full. Increase MAX_TRACKED_BC
Afterwards it continues running seemingly normally:
Loading: 11s, ETA: 0s [========================>] 8.70M/8.70M sigs Compiling: 2s, ETA: 0s [========================>] 41/41 tasks ...
I'm running version 1.4.1/27451/Thu Nov 7 10:32:19 2024 in Windows 11 Pro. At first I thought MAX_TRACKED_BC is an environment variable, but apparently it's referred in some ancient text in a language way too complex for my mind to grasp: https://github.com/Cisco-Talos/clamav/blob/52b201762f9a4bbd216dcd62b82a0287a0695b07/libclamav/bytecode.c#L47
1.4.1/27451/Thu Nov 7 10:32:19 2024
MAX_TRACKED_BC
Is this some error way too important for me to ignore? I mean clamscan seems to be working fine after the error messages (though I still haven't tested it enough).
clamscan
Hi,
When I run
clamscan.exe(I don't have the daemon running) it spams the terminal (20-30 lines) with the following:Afterwards it continues running seemingly normally:
I'm running version
1.4.1/27451/Thu Nov 7 10:32:19 2024in Windows 11 Pro. At first I thoughtMAX_TRACKED_BCis an environment variable, but apparently it's referred in some ancient text in a language way too complex for my mind to grasp: https://github.com/Cisco-Talos/clamav/blob/52b201762f9a4bbd216dcd62b82a0287a0695b07/libclamav/bytecode.c#L47Is this some error way too important for me to ignore? I mean
clamscanseems to be working fine after the error messages (though I still haven't tested it enough).