Sidecar crashes due to OutOfMemory error

Issue Summary

In large instances, gRPC threads on the sidecar might become stuck, causing the relevant object to not be promoted in the heap - this ends up causing the heap to grow exponentially, resulting in an OutOfMemory error. This crashes the sidecar, rendering all repositories on that node unavailable.

Steps to Reproduce

Currently, there are no known steps to reproduce this behavior. These will be added here when available.

Expected Results

gRPC threads progress as expected, allowing GC to clear out the heap for continuous usage.

Actual Results

Objects are retained in the heap, resulting in an OOM error causing the sidecar process to be terminated.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available