Should be fixed in upcoming. Reason for this behavior was that the package compiler did not remember that a particular package already failed to compile. So whenever it was triggered by certain user actions it caused quite some mayhem internally.
Oh and thanks @readme for sharing a reproducible test case.