(Version 5) Freezes on Startup (OSX Mavericks)
When i launch SoapUI community edition, it just freezes. Didn't experience that with the Beta version. My details: OSX Mavericks MacBok Pro Retina Edition
Forum Discussion
I had the same experience - SoapUI was completely unresponsive for several minutes after starting. This happened on every restart, not just the first one.
Clicking on menu bars, icons or close buttons on open 'Windows' had zero effect until the Window with the browser had completed loading the 'Welcome page'.
I found another thread about a similar issue with an earlier version of SoapUI on OSx 10.8 - they suggested that
adding <con:setting id="UISettings@disable-browser">true</con:setting> to the ~/soapui-settings.xml had fixed their problems.
I added the setting and restarted SoapUI and SoapUI 5 is a much much better experience on my Mac - I can start using it in seconds and menus, buttons etc. are responsive immediately.
It would probably be wise to run the browser in a background thread instead of letting it block the entire ui on the mac. I use an Oracle JDK early access build - but the behavior was the same on the official builds of the Oracle 7 JDK.
By the way there is nothing of interest in the log file when experiencing the "wait for minutes for the browser window to finish loading".
Clicking on menu bars, icons or close buttons on open 'Windows' had zero effect until the Window with the browser had completed loading the 'Welcome page'.
I found another thread about a similar issue with an earlier version of SoapUI on OSx 10.8 - they suggested that
adding <con:setting id="UISettings@disable-browser">true</con:setting> to the ~/soapui-settings.xml had fixed their problems.
I added the setting and restarted SoapUI and SoapUI 5 is a much much better experience on my Mac - I can start using it in seconds and menus, buttons etc. are responsive immediately.
It would probably be wise to run the browser in a background thread instead of letting it block the entire ui on the mac. I use an Oracle JDK early access build - but the behavior was the same on the official builds of the Oracle 7 JDK.
By the way there is nothing of interest in the log file when experiencing the "wait for minutes for the browser window to finish loading".