Automatic heap dump on OOM versus manual on-demand dump for intermittent UI slowdown under a fixed heap limit

Goal: determine if enabling automatic heap dump on OutOfMemoryError in IntelliJ IDEA provides a reliable way to capture the IDE state for diagnosing intermittent UI slowdown while the IDE runs with a fixed maximum heap size.

Constraints: the IDE is launched with a fixed -Xmx limit; automatic dumps guarantee capture at the cost of ongoing disk usage and potential exposure of sensitive project data, whereas manual dumps via the Help menu avoid persistent files but require the user to trigger them during the symptom window and risk missing the event. Additionally, the exact location of the heap‑dump controls can vary between IDE versions.

Questions: Should the automatic heap‑dump option be kept enabled in a regular development workflow given the trade‑off between diagnostic completeness and disk accumulation? Does the manual on‑demand approach provide sufficient diagnostic value for intermittent UI slowdown when the heap limit is fixed? How does version‑specific placement of the heap‑dump setting affect the decision?