Skip to content

Commit a96c5cf

Browse files
committed
[scudo] Let allocator config limit the page releasing interval
On Android, this interval constraint was used to avoid increasing the memory pressure by a long interval. Now the memory footprint is managed better and we always do a M_PURGE call before changing the interval. It's better to remove this legacy constraint.
1 parent bab0507 commit a96c5cf

File tree

1 file changed

+0
-8
lines changed

1 file changed

+0
-8
lines changed

compiler-rt/lib/scudo/standalone/wrappers_c.inc

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -251,14 +251,6 @@ INTERFACE WEAK int SCUDO_PREFIX(mallopt)(int param, int value) {
251251
// M_PURGE call so that we can minimize the impact of any unreleased pages
252252
// introduced by interval transition.
253253
SCUDO_ALLOCATOR.releaseToOS(scudo::ReleaseToOS::Force);
254-
255-
if (value == 0) {
256-
// Will set the release values to their minimum values.
257-
value = INT32_MIN;
258-
} else {
259-
// Will set the release values to their maximum values.
260-
value = INT32_MAX;
261-
}
262254
}
263255

264256
SCUDO_ALLOCATOR.setOption(scudo::Option::ReleaseInterval,

0 commit comments

Comments
 (0)