Compaction module seems to get stuck

During cross-space compaction, sometimes due to the selection strategy of the selector, the system may execute compaction tasks that require a large amount of memory. The memory demand of a single compaction task may be larger than the total memory size allocated to the compaction module by the system. In this case, these compaction tasks will be stuck at the memory allocation step, waiting indefinitely. Subsequent compaction tasks cannot be executed either, making the compaction module appear as if it has "stopped".