Heh. I have that problem too on my v3.3.2 on Win 7 VPS.
I slam the "CANCEL" buttons after I wait a good 3-4 minutes. I have to cancel many times to get control back because I have tons of trading pairs.
The work around I've found is to re-create the trading pairs I want, hit SAVE, then START. i.e. I let it start and after it takes too long I hit cancel a bunch of times. Whatever pairs aren't started properly I CLOSE. Then I re-create the pairs, hit SAVE, then START. It's slow but it works for me.
I have two instances of v3.3.2 running. One for BTC pairs, and one for ETH pairs. I've never had issues with the ETH trading pair instance.... which makes me think that the Jsongui issue may be related to running too many pairs in one instance of the bot. My BTC instance has a ton of trading pairs all running in full BB.
I suspect Cryptosticks is correct. It has something to do with resources allocated to each instance of jsongui running a trading pair. I'm still learning how to tweak XT, so I'm still running pairs on 3.3.2
I've noticed that GunBot slows down considerably, and lately, after starting about the 6th trading pair (manually, the way Cryptosticks describes). It will only run for a few hours or overnight before jsongui crashes. Is this a case where more memory needs to be allocated to the java heap or something? Gb Devs? Buehler? Buehler?
I would really like to know how to resolve this. Even after switching over to XT, I'd still like to setup another box with my ol' pal 3.3.2 on it without problems. Any software that pays for itself within the first two weeks deserves to be kept running.
BTW, this is not running on a VPS, this is on a spare engineering workstation I have with two E5-2623V3 3.2 Ghz processors and 16GB of RAM. Available resources are not a problem.
Nothing else running on the system except 64bit Win-doze 7 (for now) and the usual crapola for an older nvidia graphics card.