Skip to content

Commit da73b5c

Browse files
committed
fix incorrect usage of memUsedPool in case of full blocks
1 parent 1017b3d commit da73b5c

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

src/mmdata.c

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -139,10 +139,11 @@ vstring g_qsortKey; /* Used by qsortStringCmp; pointer only, do not deallocate *
139139
*
140140
* offset -3:\n
141141
* If this block has free space at the end (is \ref fragmentation
142-
* "fragmented"), then it contains its index in the used blocks array, see
143-
* \ref memUsedPool. A value of -1 indicates it is either fully occupied or
144-
* totally free. In any of these cases it is not kept in the used blocks
145-
* array.
142+
* "fragmented"), then this value contains its index in the used blocks
143+
* array, see \ref memUsedPool. A value of -1 indicates it is either fully
144+
* occupied or totally free. It is not kept in the used blocks array then.
145+
* If this block becomes full in the course of events, it is not
146+
* automatically removed from \ref memUsedPool, though.
146147
*/
147148

148149
/*! \page Pool

0 commit comments

Comments
 (0)