@Artyom I never experience such error on my side. Can you please try the latest version to see if the problem still exists?