We're working on optimizing memory consumption by sharing configurations across like-instances (instances of the same class). This is dramatically helping in memory management which is the problem you see above (which is happening in Windows in large projects).
Sencha Architect Development Team
In spanish we say: "El que espera desespera" in english is something like "He who waits, despairs"
I have a big project too, and I like SA a lot, I want to use SA to do the project, and Im desperate waiting SA version 2.1
I have not stopped the development, Im doing the Controls, Stores and Views.
Views... I do one by one in SA and backup in another folder,
when the View is ready Im moving the files:
app\view\lastView.js and metadata\view\lastView to a backup folder and start with another View,
so far it has worked when I restore the files to the \view\ folders to edit in SA
Continuous the good work,
SA v.2.1 we are waiting for you!.
Same SA2 and machine details as in my starting post.
I fixed the project already, but I can tell you how it happened. I duplicated a panel and got those errors. I deleted the nested components of the panel one by one till the message went away. It's looks as though (uneducated guess) when a component is duplicated, some of the parameters don't get copied from the nested items.
It was a Window, with field containers, each field container contained multiple fields which included textfields and datefields. Looking at the forum, I can see several people experienced the same thing and have sent their projects to your team.