Group: StrataFrame Developers
Posts: 6.6K,
Visits: 6.9K
|
Same issue, same problem. When a handler is not released, the object cannot be disposed. Thus you get a memory leak. That is why it is so important for all controls to work within the confines of the framework and interfaces used therein. In this example, the DevExpress controls that use attach to the IEnumerable interface are not releasing the handlers as expected. Thus, a memory leak. Again, we will see if there is something we can do to accommodate all 3rd party controls. But here is one thing that I have already proven. We can use a Custom BBS and an XtraReport with no memory leak whatsoever. This is a very common control and combination of tools used by SF users. Some of our largest users also use the XtraReports within massive applications. And if they were experiencing memory leaks like you have described, there would be mass chaos. The DevExpress web grid is another story, however, as most people take a different approach, as I have mentioned in previous dealings with your current issue.
Regardless, I would love nothing more than to find a solution on our side so we can get this behind us.
|