I've been running GoTo on Mac that also runs VMware Fusion (running Win64 instance in VMware) reliably for several years. With a recent GoToMeeting update, some softwware bug was introduces that completely crashes the Mac (verified on Mojave 14.5, 14.6 which has been an extremely stable OS X version). It's happened right when GoTo starts, as well as soon thereafter-randomly. I also successfully ran GoTo within Windows on VMware (vs. running on Mac), but then that completely crashed the Mac as well the next day (i.e., black screen of death, nothing responds, have to reboot). This way of completely crashing OS X Mojave from within a VM as well as outside the VM sounds hard to do if someone tried to do so, but latest (or near latest version, running 8.46 GoTo) is doing just that.
I contacted GoTo Phone support and they were not helpful (broken English communication challenges, no possibility for escalation of issue, no option to obtain prior version of GoToMeeting). My mistake in trusting GoTo with automatic updates--I turned this feature off. I used to do manual updates and have prior versions on my Mac "just in case" but in one of my computer replacements and re-install of GoTo, the default auto-update was enabled. Another lesson learned!
Does anyone know where prior versions of GoTo for Mac can be obtained... Thanks for any assistance you can provide.
Main takeaway for future reference:
1. Turn GoTo's auto software updates since, according to their support staff, these are not available from GoTo support.
Suggestion for GoTo -LogMeIn support:
Unless I was provided misinformation by your support, I'd highly recommend having a location available with prior software versions for customers. Thank you!
@PJ4 I'm sorry to hear about this poor experience with your Macintosh machine.
While we sometimes roll back new versions that experience unexpected results across many users, we do our best to retire older software versions within a few months of release. If you'd like to private message me with your GoTo login email, I may be able to set you back a build for the time being until we look further into your existing case.
I'm not aware of any other reports of GoToMeeting overloading Mac processes etc, and will keep tabs on this thread for any similar experiences.
OK, we will most likely require log files from an affected machine, when you have about 20-30 minutes to document the environment with Customer Care. Technically if you are inside the VMWare, GoToMeeting wasn't designed for that environment, but it should not conflict with VMWare running on the side.