Daniil Gentili

The problem with making this mandatory is that in some cases, side effects are the only reason why a file is included. Also, with scan order being non-deterministic in multithreaded...

Decided to not merge this after all, as it introduces yet another element of non-determinism, without any strong reason in favor (performance issues can be solved using the newly added...

This is caused by the OS killing the Psalm worker due to an OOM, try running with --debug and --debug-by-line to see what file is causing the high RAM usage

I still need a proper reproducer to help

Please try using the official docker image, instead

6.13.0 with the arrayCache="false" config should help with this.

This is not a bug, it's just an OOM, which is now visible: further increasing swap space should fix the issue.

Is the swap completely filled up during execution? If yes, further increase it

True, but it's more explicit this way.

@trowski / @kelunik done!