Hello,we discover a strange problem when using the UltraToolbarsManager.On one form we have placed an UltraToolbarsManager wich contains some ribbon tabs with groups and ToolButtons. The images uses by the buttons are stored in ImageLists wich are connected via the ImageListLarge and ImageListSmall properties of the UltraToolbarsManager.When the application is started the Windows TaskManager shows, that the memory usage is increased every time the mouse is moved over a button. It look like as if the images was loaded again and again. After a while, the buttons (no only the images!) on the ribbon group where the mouse cursor is currently oved over disapear or the ribbon groupis displayed as a red framed box with a red cross in it. After some more time when moving the mouse over the remaining buttons of other groups the application crashes.Btw. there are no events handled when moving the mouse.Does anyone have an idea how to solve my problem?Best regards.
It sounds like there is a memory leak here. I have forwarded this post to the Developer Support Manager and a DS engineer will be contacting you about this issue.
Infragistics has corrected the memory leaks in the 2010 Vol 1 version. The memory leaks had to do wth the objects not being disposed automatically (you had to force them individually which was a pain) because of the color change event and theme change event.
What color change event are you talking about?
I have this problem of constant leaking on 8.3 when hovering over tool bar buttons and have set both themes and app styling to false...
AE
The more I look on the web and then into my own project I find more and more problems...
Apparently Infragistics decsion to hook up their controls to static events is what kills it in terms of memory...
A huge issue is when you assign an image to ANY control in the suite...apparently each time an image is accessed it is replicated and not released...
This really bites big as I do not have funds to upgrade and have invested thousands of hours into this project...
I think I am going to gut the whole program and go to the VS .NET controls and hopefully keep the docking and tabbed mdi...
Totally bummed out...
Replicate this by simply putting a tree control on a form with some images...create a tree structure...
Make sure that when all of the images are expanded they invoke the scroll bar...
Pull up the task manager performance monitor and watch "Private Memory"...
If you scroll the control or expand nodes the memory spikes out of control...
Eventually the garbage collector picks up on this and dumps all of the garbage left by the tree...
Now do the same thing in the VS IDE....scroll your solution explorer...expand nodes...the memory never spikes at all...
I don't know what is going on here but it is extremely disturbing that the Infran controls, though full of cool features, are horribly designed in the back end to collect their own garbage...
Ugh
I am digging deeper and deeper into this and their is somthing seriously wrong with this control suite...
Populating a tree view control with about 150 nodes broken into 5 levels...
Some have images, most don't
Running in Win 7 64, when you simply scroll the control...the Private Memory consumed spikes astronomically...
An application that normally resides at a peaceful 64,000kb spikes to 500,000 kb...sometimes more...simply by scrolling the tree control...
If I force a garbage collection or private mem check a few times it eventuall settles back down..to 64..
In one instance, simply expanding one node on the tree, doubles the size of private memory...to show 20 child nodes...
There is somthing totally screwed up here
Out