You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the function _duma_allocate(), during the loop where we try to find the free slot, even after finding the free slot and 2 empty slots, we run through all the slot structures. If I am correct, by design, the empty slots come after the free slot, so after we find the 2 empty slots, shouldn't we break the loop?
} else
#endif
if (DUMAST_EMPTY == slot->state) {
if (!emptySlots[0])
emptySlots[0] = slot;
else if (!emptySlots[1])
emptySlots[1] = slot;
**else
break;**
For example,
test program tstheap with a test duration of 10000 runs for 160 seconds without breaking the for loop, and runs 120 seconds with breaking the loop.
The text was updated successfully, but these errors were encountered:
Hi,
(for the linux environment)
In the function _duma_allocate(), during the loop where we try to find the free slot, even after finding the free slot and 2 empty slots, we run through all the slot structures. If I am correct, by design, the empty slots come after the free slot, so after we find the 2 empty slots, shouldn't we break the loop?
For example,
test program tstheap with a test duration of 10000 runs for 160 seconds without breaking the for loop, and runs 120 seconds with breaking the loop.
The text was updated successfully, but these errors were encountered: