Hi! Could you please check whether you can replicate this issue with the latest released version of the package (4.7.0.1)? We believe that this crasher has been fixed upstream, but unable to reproduce the problem to check this assumption. -- Sincerely yours, Yury V. Zaytsev