First of all, I want to say Indigo is really great.
However, I have got some problems with a project that goes beyond a few pages / states.
I particularly use screen states a lot and once you quite some state, memory use is through the roof. In some instances I had the application using up 1.5 - 2 GB of RAM. Is this normal or is it a memory leak?
Furthermore, after a while the application gets really sluggish and switching states sometimes takes up to 10 seconds. OK, I'm not using the latest of the latest hardware, but the PC is decent enough so it shouldn't have to much problems handling Indigo.
Hi Kenneth,
What do you mean by "quite an state"? How many states do you have in your screen?
We'll work in improving memory management soon.
Thanks a lot for reporting.
Best regards,
Diego
Hi,
Well I have about 30 different states in a screen and normal memory usage is around 1.5-2GB RAM now, while sometimes CPU is around 50%.
The fact that's 50% tells me it's actually using 1 core at 100% and not using all (2) the cores that are available. Apart from that it's now also slowing down (a lot) and having regular crashes (sometimes it pops up the error dialog, sometimes it just shuts down).
Hi Christine!
The thumbnail rendering can become a lag on large flows, or with screen with a lot of controls (especially heavy controls like grids).
Though we are constantly looking for ways to improve it, one thing I can recommend if you are going to do many operations on the interaction flow, is to disable thumbnail rendering and show labels instead. You can do that by clicking on the Overview Map toggle thumbnails button:
(As shown on the Understanding Screen Interactions & States topic)
Let me know if that helps!
Santiago.
Indigo Studio Team.
I'm experiencing the same issues on Indigo Studio v1 update 21. My PC can more than handle the required needs to run the program (16Gb RAM, Core i7 processor), but it lags when I have multiple screens. It seems to lag most when I move to the Screen Interactions layout as it is attempting to render all of the screens I have. Then I click on one to delete it, it needs to then render a larger thumbnail of that, delete that screen, then it needs to re-render all of the other screen thumbnails again. It's this constant rendering that causes it to hang (at least from what I can tell).
Hi Diego,
Unfortunately I cannot share the screen with you because of confidentiality contracts.
Here is some information about the screen:
I reckon this is normal behavior and the memory usage is what one would expect with such a big screen. I think the lack of certain features has forced me into using a single screen instead of various screens. I used a single screen, mainly because I'm modeling a web page and I want the navigation to be consistent accross all pages. Since I don't want to copy paste it, what I basically do is create a new state, remove everything but the navigation and build up the new screen in the new state. This of course has caused me to use a lot of screen states, where actually a new screen would have been more appropriate.
If there would be a way to componentize certain groups of controls I could have created a navigation-component and included it in all the different pages. I don't want to copy the items on every page because having to change something in the navigation would force me to change about 45 pages, so I don't want to do that.
Hi again Kenneth,
I'm really sorry to hear this. Is it possible for you to share that big screen with me? drivero at infragistics.com
In case you can't share it, maybe you can help me reproduce the scenario. Here are some questions:
- Do you have large images, lots of icons or tables inside that screen?
- Do you have other screens opened or any storyboard?
- Does this always happen with that screen or sometimes you can work fine with it?
Thanks again.
Regards