We've recently been notified by some users of browser crash issues while using the new editor. Our team has been able to reproduce and identify this problem and works actively on a permanent solution.
Our first investigations show that this situation occurs when the users are translating quite long documents while short documents are not affected. This is a memory management issue that occurs when navigating through the editor pages, which eventually forces the browser to close the tab to free-up memory because a limit has been reached.
On 22 July, our technical team has identified the root cause of this behaviour and they are actively working on a solution. It will take some time because the root issue affects the core of the editor application, and therefore adds some complexity to the permanent resolution of it.
UPDATE on the situation with the Editor crashes and performance degradation.
We have identified the root cause of the issue and are working on fixing it since some time now. But this fix takes time and requires proper testing.
Meanwhile, we will release a temporary patch which will refresh the Editor from time to time to prevent crashes (the equivalent of manual F5 refresh). This is not the most elegant solution, but again - It’s a temporary solution to prevent crashes.
The structural fix will be released as soon as possible. This is a top priority for the development team. We will keep you updated on the status of the issue.
We use this opportunity to tell you that we are sorry for the difficulties you may have encountered as a result of this problem.