FIX. RadCommandBar - memory leak in the RadCommandBarOverflowButton
- Add RadCommanBar to a form and the shown and close the form several times.
Posted on:09 Feb 2016 08:17
I am glad you are happy with our product. In regards to "buying the original one" I am not sure what do you mean by that. However, what I can advice is to contact firstname.lastname@example.org with your sales enquiries and they will help you in the best way they can.
I hope that you find this information useful.
Posted on:08 Feb 2016 20:29
Thanks Stefan for your response,
In the latest version 2016, this memory leak is fixed. I had v.2014.
Thank you Telerik for your amazing component. may I be honest: I am Iranian and I don't have any way to buy this component from your company. Could you please show me a way to buy original one.
thanks a lot.
Posted on:08 Feb 2016 10:51
may I please ask you to open a support ticket regarding your case and provide us with a sample and/or description how to replicate the observed leak, so we can log and handle it accordingly.
Posted on:05 Feb 2016 17:38
I have same problem with radGridView. I attach my memory snapshot and the instance retention graph.
After further investigation we found that in the custom application there are two CommandBarStripElement which does not belong to the RadCommandBar in the Designer.cs file.
In that case the CommandBarStripElement should be disposed manually or should be removed from Designer.cs. Please refer to the code snippet below which cause the issue with memory leak:
this.commandBarStripElement3 = new Telerik.WinControls.UI.CommandBarStripElement();
this.commandBarStripElement4 = new Telerik.WinControls.UI.CommandBarStripElement();