It's not fun when you have spent the morning making changes to your app and then suddenly the configurator bombs out as a result of an inherent memory leak that has prevailed for some time.
This results in all your work being lost even though you have been pressing the save button at every corner. The only way to prevent a loss of work is to put it under the test, this is the only way of securing your work. So don't be fooled by the current save button, its a false sense of security
Memory leaks of this nature should be resolved, the configurator reports numerous errors from time to time moving between forms setting up choices adding rows to choices etc etc . While they don't always lead to the configurator hanging, it is an indication of something lurking in the background.
If you have a large visual perspective with numerous menu items and proceed to make changes moving between items back and forth eventually you will get a java stack overflow error, and then you done, prepare to start all over. This is the one area that almost always leads to a memory leak error.
