Yes, you should delete the MeshGeom -- when the GUI is operating, it keeps track of the last MeshGeom and deletes it before running a second time. After you do a start/stop cycle, it forgets that information and ends up creating a MeshGeom that is on top of the existing one -- which causes the crash.
In general, you probably don't want to save MeshGeom's to the *.vsp3 file. They are very large and can be easily re-created next time. Every time you update a parameter, they are out of date, so I make a habit of deleting them unless I have a specific need.
The spanwise load distribution for thick-surface (Panel) method is a very recent addition and is still getting debugged a bit. It is likely smoother if you use the 'experimental file format' for Panel method. Or, if you use VLM instead, it will be much better.
The case with the very low Cp is a case at zero alpha. If it is a VLM case, then the very low delta_Cp's don't surprise me at all. Otherwise, I would need to dig into that case.
Rob