### Describe the bug Using a hash join may lead to OOM kills / very large memory consumption even when a memory limit is set. ### To Reproduce No reproduction steps yet. We have a flame graph from a prod environment though:  ### Expected behavior Memory manager report "out of memory", the query fails. ### Additional context I think the code only tracks `HashJoinStream::visited_left_side` but `build_equal_condition_join_indices` is completely untracked.