|
From: Philippe W. <phi...@sk...> - 2011-10-02 20:23:13
|
I have just attached a patch to https://bugs.kde.org/show_bug.cgi?id=250065 to have better error messages and/or detect more dangling pointers errors when big blocks are freed. Basically, the patch * releases blocks from the freed queue before a malloc, not after a free * releases big blocks in preference to small blocks. Min size of big blocks is defined with a new option --freelist-big-blocks For this new option, I hesitated between two techniques: * Specify a percentage of the --freelist-vol * Specify an absolute value in bytes. I find the absolute value easier to explain/understand/use, but a percentage might be more "self-tuning" if the freelist volume size is changed. Any feedback about this ? Philippe |
|
From: John R. <jr...@bi...> - 2011-10-02 21:36:49
|
> For this new option, I hesitated between two techniques: > * Specify a percentage of the --freelist-vol > * Specify an absolute value in bytes. Specify a percentage of --freelist-vol, but also a minimum size. For example: "big" means >=1.5% of the total size of the blocks on the freelist, but no less than 300kB. [Obviously this depends on the application, and on a knowledgeable user.] -- |