Cancel button on decompilation phase when trying to save a candidate will not work on high memory loads

[TheAmg]

Describe the bug

If the system you are using unlogged with has low available memory and you try to cancel the decompilation phase (before seeing the confirm option), it will not cancel. This leaves the user stuck, in need of force quitting Idea.

Reproduction steps

1. Load up your system with a lot of applications (get to very high ram usage)
2. DirectInvoke a method that returns a very large response, try to save this candidate. The method should take a long time decompiling as you click on save. Alternatively try to save many candidates.
3. Click on cancel
   ...

Expected behavior

For there to be no UI blocker if the user wants to cancel.

Additional context

No response