Ever since the upgrade to 10.1.1, many developers have been reporting an issue with Framework Manager. At some point during the development, Framework suddenly starts crashing whenever they delete or move specific items from the model. Frustratingly, trying to fix the issue by importing the model into a new model tends to copy the same problem.
The error in question is as follows:
Invariably, the developers would be frothing at the mouths because either they forgot to save their changes when it crashed, or they have saved their changes, and now they don’t have a way to revert back to before it started crashing like this.
The manifestation of the bug tends to follow a similar pattern. The models are generally complex, old, and contain more than one package. Some models that exhibit this bug have security, and some don’t. Deleting some fields trigger the bug, and some fields don’t. However, because the crash only happens with specific data items, it makes it easier to track down where the problem is.
In this case, a simple verify model explains what the issue is:
A glance at the model.xml shows that, somehow, there are two security views with the same name.
The easiest way to fix the problem is to delete one of the duplicated securityView nodes. There is a risk that Framework will continue to crash if the remaining securityView contains references to deleted objects, so at the very worst you can paste in:
<securityView><name>GO Sales (query)</name><definition/><access/><functionSets/></securityView></securityViews>
If this happens, you will have to redefine the package definitions, but at least the model will be viable again.
EDIT: Lose your work after the crash? See here on how to recover everything!