User Interface is not responding

image

Good day

I updated to the new v5.4 today and everything went smoothly. I did some work on a workflow and when I wanted to save I got the error “An unresponsive user interface has been detected”. It does this for all of my workflows.

I have the options “Save and restart” and “Wait for the UI to respond”. Using the latter doesn’t work as the error appears a few seconds later. I tried “Save and restart” now and upon loading another workflow the error appears again.

Any idea what could be causing this? Is there perhaps a way to rollback the update or revalidate the knime system files?

I too am seeing this popup appearing quite a lot in KNIME 5.4, although generally I have not needed to save and restart, and pressing Wait, maybe a few times has kept it going.

My laptop is quite often low on resources especially hard drive, but I am running it side by side with 5.3.3 yet haven’t noticed any particular issues in the older version. Having not seen the message in earlier versions, I believe it is new to 5.4, as a kind of safety net, and wonder if it is a little over-zealous in appearing?

I’m still getting this error daily. Maybe a few times an hour. Sometimes as often as once every 5minutes.

Hi,
right before the warning pops-up, do you have the feeling you can’t interact with the UI anymore (because it’s somehow frozen)? Was there some specific action you did before it came up?
Because we introduced the pop-up to make sure no work is being lost in case the UI is frozen. However, we didn’t expect it to happen that often (or at all) and was more as a safe guard for an unlikely event.

In any case, please add -Dorg.knime.ui.disable_healthchecker=true to your knime.ini in order to disable it.

3 Likes

Thank you for your suggestion, I’ll implement it and give feedback after an extended period of work.

No usually there’s nothing noticeable that happens before it triggers. I’ll be working on a workflow, it triggers, I tell it to wait, then I continue as normal. Then a few minutes later it triggers and I do the same.

I will say however that it triggers more reliably on workflow load and save, and more on certain workflows than others but there isn’t any discernible difference between them which could cause the difference.

I’ll keep this post updated.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.