When I said terminated by a signal, I meant anything where another program kills the slickedit process. So, for example, using xkill to kill the SlickEdit window, or having the window manager decide SlickEdit is not responding when logging out, and asking the user if it should just kill the process. Things like that.
There's a lot of settings in the state file. Most of them actually got restored, because we keep a lot of information on config changes outside of the state file, so we can do upgrades between versions. But since this wasn't really an upgrade, some settings didn't get transferred.
Probably the quickest way to deal with lost settings is to get out of slickedit, rename the bad state file back to vslick.stu, start SlickEdit, bring up the options dialog, and export all of your options. Exit SlickEdit again, rename the bad vslick.stu to get it out of the way, restart SlickEdit, and then import the options you exported. At the very least, when I use your vslick.stu, I can export everything without running into any obvious trouble.