(I didn't find this in the forum)

Hi, should I care when I get that error after updating the database:

[DllMain] Error setting up low-fragmentation heap: 50

It's not the first time I've been getting that error, it started... I don't remember, maybe with 0.95.2 or 0.95.3.

And I never took the error very serious as, having a look to the update log file and the growth of the database file, the database gets updated, but today I decided to ask.

Well, any information it's appreciated

Regards.


P.S.: the latest update, just for curious out there:

ClamAV update process started at Sun Jan 24 17:38:22 2010
main.cvd is up to date (version: 51, sigs: 545035, f-level: 42, builder: sven)
Downloading daily-10323.cdiff [100%]
Downloading daily-10324.cdiff [100%]
Downloading daily-10325.cdiff [100%]
Downloading daily-10326.cdiff [100%]
Downloading daily-10327.cdiff [100%]
daily.cld updated (version: 10327, sigs: 157816, f-level: 44, builder: neo)
Database updated (702851 signatures) from clamav.n2000.net (IP: 80.80.88.40)
[DllMain] Error setting up low-fragmentation heap: 50

--------------------------------------
Completed
--------------------------------------

strange I need to check if the error is "unsupported" (the error means this)
it's harmless anyway, it's a trick for clamd to reduce memory usage on database reload
you can just ignore it, I'll change the message to not display it when the function is not supported by the os

btw what is the os?

Windows 2000 with SP4 working on NTFS partitions with 4KB cluster size (I don't know if this could be important as I know file systems differs, even if it's not the same kind of fragmentation)

(I knew I should say before, sorry )

In my humble opinion, if this is supported on XP (I don't know as I don't have it installed on my XP partition), it shouldn't be hard to make it possible under 2K (they are almost twins (by "minutes")) I hope it instead removing the warning

nothing to do with the filesystem, is the memory fragmentation

anyway I've fixed the warn, the next version will have this fix

if you want this feature on win2k you may need to install this hotfix

http://support.microsoft.com/kb/816542 http://support.microsoft.com/kb/816542

but it's only usefull for clamd, not for clamscan

Thanks for the info

I supposed that could be the memory fragmentation, but here, my knowledge is limited. I admit.

In the other hand, thanks for the information and link to Microsoft.

P.S.: It looks like the post SP4 update rollup hotfix has this fix included (at least the file versions are later). I have it here but not installed (long story) I'll install and I tell if the error disappears.

the concept is similar a program asks system for memory then disallocates it, the system has a list of blocks of memory of a particular size, giving pieces to programs can lead to have enough non contiguous memory, this makes difficult to give consecutive memory for the size requested, so some blocks are too small and cannot be used if the programs needs a greater size
(yes a bit confused but I hope you got something )

http://en.wikipedia.org/wiki/Fragmentation_%28computer%29 http://en.wikipedia.org/wiki/Fragmentation_%28computer%29

Unlike other types of fragmentation, internal fragmentation is difficult to reclaim; usually the best way to remove it is with a design change. For example, in dynamic memory allocation, memory pools drastically cut internal fragmentation by spreading the space overhead over a larger number of objects.

on linux acab implemented a memory pool to reduce this problem, on windows I'm using a windows api help, that gives similar advantages

Ops, editing while you replying.

Thanks for the info again

Confirmed, the post SP4 Update Rollup for Windows 2000 carries the fix and the error doesn't appear now.

But, even if the fix is good for the system, I think I'm going back to SP4. From my experience, the Rollup leaves more issues than fixes on the system, at least in my personal case.