Crashes constantly - out of memory

[PlasmaTek]

Support are ignoring me on this one, can anyone give me an update on this? Should I give up hope and assume that SA2 will never work for bigger projects?

[PlasmaTek]

Capture3.jpg

[aconran]

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).

[paulcardo]

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

While waiting....
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!.

[Phil.Strong]

Also see how another community member is working cross Architect project https://github.com/tomz/st2-model-store-share

Thanks @tomzeng

[PlasmaTek]

This is another one I keep getting. This a brand new project with a couple of views and stores. I deleted a component and then I get this.

[Phil.Strong]

assume build: 442

could you send us the project so we can find out what's going on?

[PlasmaTek]

Hi Phil

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.

Any chance of a beta SA2 with the crashing fixed?

[Phil.Strong]

What component types did you have nested?

That would help us try to reproduce

[PlasmaTek]

What component types did you have nested?

That would help us try to reproduce

Hi Phil

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.