hi !!
i have a form with 4 grid that are connected to each other via data relations.
the grid have some checkboxes, textfields and dropdowns.
total around 10 datatables.
when user clicks reload on data and to a grid.datasource = ds on the tables again. for some reason the data isnt released.
1. is it possible to prevent initializelayout to be called (first time should be enough) ?
2. whats the correct way of doing this ?
i use 2008 vol 3, but have also tried with 2010 vol 2.
regards,
Geir Sanne
Hi,
This doesn't sounds like it's related to the previous posts in this thread. I don't remember hearing of anything like this happening before.
What kind of DataSource are you using here?
Are you using the same instance and adding/removing rows of data? Or are you creating a completely new instance of a data source?
I can't imagine anything you could be doing in you code that would cause this behavior, unless you are simply adding rows to the existing data source without realizing it. Assuming that is not the case, then it seems like it's probably a bug in the 4-year-old version of the controls you are using. You could try getting the latest service release.
Can you post a small sample project demonstrating this behavior? If so, we could try it out and tell you for certain.
If not, then you may want to try getting the latest service release or updating to a new version of NetAdvantage.
How to get the latest service release - Infragistics Community
Did anything come from this? I am having an issue with UltraCombo in that each time I set the datasource, the InitializeRow() event fires for the new data as well as the previous data as well. So, each time the DataSource is set using SetDataBinding(), the number of times the InitializeRow() fires grows based on how many records are in the different datasources.
SetDataBinding having 1 record, InitializeRow fires once.SetDataBinding having 2 records, InitializeRow fires three times.SetDataBinding having 1 record, InitializeRow fires four times.
We are using version 8.1 of the WinForm controls.
Thanks for any light you can shed on this...
Here's a sample project that shows a memory leak.
1) Click on the [New Data] button a few times right at he start, no leak.2) Filter the third coumn, select "hello2"3) Click on the [New Data] button afterwards... now there are leaking objects. And there are more leaks added eevry time you click the button after that one filtering.
The DataTable is disposed.
Did you try this with the MS DataGridView? I'm pretty sure the WinGrid has no control of BindingContext HashKey objects. That looks like something internal to the BindingContext. It's possible that the WinGrid causes more of these to be created than the DataGridView, since the WinGrid show hierarchical data and the DataGridView is just flat. But there's not much we can do about that.
The MouseEventManager could be an issue in the grid, but it's something we would have to look into at length and I won't be able to do that in a forum post.
I'm going to forward this thread over to Infragistics Developer Support so they can write this up for developer review using your new sample.
i use windbg as profiler.my bad. i just saw bindingcontext..didnt see the hashkey after.
ive uploaded the sample code (more like the one we use in real app). this use about 20 mb when it starts and the memory usage just increases. when i run sci-tech it says something about direct event handler roots(infragistics.win.controluielementbase.mouseeventmanager).ive tried to remove all eventhandlers i have, but i still get this error.for some reason this doesnt occur in the last sample i sent.
there are a lot of other extra objects in memory too.. is it supposed to be like this.. no memory is freed until mem usage reaches max mem in my computer ?
i will try to run the app for 1 week see if i still get out of memory exception.