UI deadlocks much worse in 4.5.2
The UI deadlock issue in SoapUI in the windowed interface is much worse now in 4.5.2 than it was in 4.5.1, where it was usually limited to DataSource loops. Now it is pretty much whenever a suite or testcase is running, I am petrified to bring a different request window to the foreground because more than half the time, this will cause SoapUI to freeze.
It is almost completely unusuable now.
This issue is covered in a number of places not least of which SB's own bug forum: viewtopic.php?t=16472
What is baffling that they put out 4.5.2 and didn't fix this, neither did they upgrade Groovy which is now about two years out of date. I really wonder what was added to 4.5.2 over 4.5.1, that is, other than adding in three times more deadlocks!
It is almost completely unusuable now.
This issue is covered in a number of places not least of which SB's own bug forum: viewtopic.php?t=16472
What is baffling that they put out 4.5.2 and didn't fix this, neither did they upgrade Groovy which is now about two years out of date. I really wonder what was added to 4.5.2 over 4.5.1, that is, other than adding in three times more deadlocks!
