IDEA Run Configuration Timeout Enforcement Gap

IDEA run configurations expose a Stop button that sends SIGINT/SIGTERM to the underlying process, enabling user-initiated cancellation. The IDE does not provide a native wall-clock timeout enforcement, meaning external tools that ignore or suppress interruption signals may remain active despite the Stop action. This gap between IDE-managed cancellation and process-level signal handling raises questions about the effective timeout boundary for run configurations across different IDE versions and external tool implementations.

To what extent can IDEA run configurations guarantee process termination after a specified duration when the launched application does not respond to standard interruption signals?

• Does the IDE impose a hard timeout ceiling independent of the application's signal response?
• How does cancellation behavior differ between built-in IDE tasks and externally launched processes within the same run configuration?
• Is there a configuration flag or parameter to enforce process termination after a specified duration regardless of signal handling?