The memory issue I'm noticing is because of the complex visuals we're using in the windows; currently the memory usage increases by 20mb with each window I open, which isn't itself a problem. I think the root of the problem is that XamWebDialogWindow is unable to be garbage collected, so this memory is never released.

I tried to create a sample project utilizing RestrictInContainer, but I was actually never able to GC the windows, regardless of the setting. How is one supposed to manage the lifetime of a XamWebDialogWindow? I add it as a child to a panel somewhere, and remove it from the panel when the window state changes to Hidden. Shouldn't this be enough?

Reusing one window isn't possible because the user may have any number of windows open simultaneously; they must be garbage collected.

Hello Jason,

I was tried to reproduce this issue but the memory was down after I closed all of the dialogs.
I have test this with VS performance tools, can you tell me how you test this behavior? Please make sure that you are using the latest service release. Also I am recommending you to create new instance in the function you need to show WebDialogWindow in this way the dialog memory will be released after you closed it, otherwise the memory will be released after the parent page is closed and getting disposed.
If you still has issue with this, would you mind id you share small sample to investigate it more deeply.

I hope this helps.

Sincerely,
Dimi
Developer Support Engineer
Infragistics, Inc.

We noticed the same issue in our application. We got around it by searching for an instance of our window in the Children collection property and calling the Show() method on it to re-use the window rather than create a new one.

        private void button1_Click(object sender, RoutedEventArgs e)

        {

            XamDialogWindow window = null;

            // if the window exists don't create a new one

            foreach (UIElement elem in grid1.Children)

            {

                if (elem.GetType() == typeof(XamDialogWindow))

                {

                    window = elem as XamDialogWindow;

                    if (window != null)

                        window.Show();

                }

            }

            if (window == null)

            {

                // it doesn't exist so create a new one

                window = new XamDialogWindow();

                window.Content = "MyWindow";

                grid1.Children.Add(window);

                window.Maximize();

            }

            window.RestrictInContainer = true;

        }

Hello,

Thank you for the detailed clarifications. I think that this is a issue and we need to look at it. I have created case (CAS-45490-02YYYW) for you and I will forward this behavior to our development team.

I will contact you in the support case for more information.

Sincerely,
Dimi
Developer Support Engineer
Infragistics, Inc.