When this happens, can you take a look at the browser console and page any errors/warnings here?

Will do 👍

It just happened to me, and I got

TypeError: newLangStr is null

Screenshot attached. At that point, I also noticed that the about two dozen or so lexemes I had curated before that one did not result in any edits.

Update: the above-mentioned edits came in with about an hour of delay (sample edit matching the screenshot above). Not sure what caused that — has the webservice been restarted?

1. I found and fixed the bug that caused the TypeError you saw. That was triggered when one clicks the other languages button and then cancel in the dialog. Fixed it, but that should not cause the tool to become unresponsive.

2. The edits that only were saved after an hour: The backend that creates the edit on Wikidata has a mechanism that edits won't be done if the server is already under high load. The parameter when this happens maxlag was set to the prescribed value for bots. Since this isn't a bot I can set is considerably higher. I just did that (from 5 to 18), so this behavior should only occur in rare cases when the servers of wikidata are extremely overused. But this again should not cause the site to become unresponsive.

Do you remember what the last action was before the site went unresponsive? And how is does this unresponsiveness become visible (only the tree man-buttons don't work or do the lanuage chooser also not work anymore)?

Ad 1: thanks.
Ad 2: makes sense.

On topic: I just gave it another try, and it took much longer than (recently) usual to get to the point when it froze. Nothing to see in terms of error messages, but the three main buttons became unresponsive, while the language selector and the other links seem to work normally. The last thing I did before the freeze was fixing the Korean gloss in the tool and the corresponding description on-wiki. However, have made similar edits on other lexemes in the same session, with no issues.

Examples of lexemes where similar edits did not cause issues: Amboss, Biosphäre.

Just had it freeze once more, again after having edited the description on-wiki and the lexeme's gloss in the tool, though this time, it froze on the next lexeme, again with no error messages.

As a workaround, I am opening the language selector and adding/ removing some text string (e.g. "simple", "test"), which revives the tool.

I found and fixed one thing that could have been the cause. Also, I added a debug-function. In the web-console you can call it with main.debug(), it prints all the state of the tool. If the bug (or other bugs) occurs toggle open the first level of the printed objects send me it's output.