Terri,
even though your problem is a serious one as well please don't hijack other threads to report it, but create a new one. These two issues have nothing in common.
To your problem: the crash comes up because of an attempt to read content from an empty sql file and has already been fixed. This fix will be available with the next release of MySQL Workbench.
In order to circumvent the crash with your current version you have to make sure the app doesn't load an empty sql file. If you can remember which files you had open before the crash either remove any empty file or add some dummy text to it.
If you cannot remember you have to remove any sql file from the MRU list (most recently used). To do this open the file ~/Library/Application\ Support/MySQL/Workbench/wb_options.xml. Search for key="recentFiles" which will bring you to the MRU list. Remove any line that refers to an sql file. After that WB should open again.
Mike
Mike Lischke, MySQL Developer Tools
Oracle Corporation
MySQL Workbench on Github:
https://github.com/mysql/mysql-workbench
On Twitter:
https://twitter.com/MySQLWorkbench
On Slack: mysqlcommunity.slack.com (#workbench)
Report bugs to
http://bugs.mysql.com
MySQL documentation can be found here:
http://dev.mysql.com/doc/refman/8.0/en/