MergedPropertyModel not releasing IPropertyModel references - Grids for WPF Forum

The latest build of this product (v24.1.5) was released 2 months ago, which was before this thread was created.

Posted 9 days ago by Andrew Stuart

Version: 23.1.3

Platform: .NET 4.7

Environment: Windows 11 (64-bit)

We are using Binding to DataObjects in WPF, and seeing significant memory leaks when the ICollection<PropertyViewModelBase> contains instances of more than one type. The MergedpropertyModel never releases the collection references.

Is this a known issue? Perhaps fixed in a later version?

We have tried setting the bound property to null briefly every time we change the collection, but this had no effect.

[Edit] We have updated to v24.1.5, and the issue is still there.

[Modified 9 days ago]

Comments (3)

Posted 9 days ago by Actipro Software Support - Cleveland, OH, USA

Hi Andrew,

Thank you for writing. This is not a known issue and I don't believe anything related has been worked on since v23.1.

Could you make a new simple sample project that shows this scenario so that we can debug with it and make sure we are on the same page with what you are doing? Please send it to our support address and reference this thread in your e-mail. Be sure to exclude the bin/obj folders so it doesn't get spam blocked. We will use that sample project to make sure any code changes we make resolve the issue.

We are close to a v25.1 release, so if you could send the sample by early next week, it would be appreciated. We might be able to squeeze an update into that.

Actipro Software Support

Posted 6 days ago by Andrew Stuart

I sent an email to support with a sample app on Friday. Let me know if you'd like more information.

Answer - Posted 6 days ago by Actipro Software Support - Cleveland, OH, USA

Hi Andrew,

Ha, I think we wrote you back about at the same time you posted this. We have a fix in place for the upcoming v25.1 release.

Actipro Software Support

Add Comment

Please log in to a validated account to post comments.