I pushed a safety check for this situation in master and 4.3 branches. Not being the developer of the module I am not sure of other possible side effects, but at least this kind of crash situation is handled now.

If the issues appears again, reopen the item.


Reply to this email directly or view it on GitHub.