A memory leak related to the automation peers of the RadPane and RadPaneGroup appears when you close a pane (using its Close button) even if you call its RemoveFromParent() method.

To work this around disable the automation peers. To do so please set the static AutomationManager.AutomationMode property toAutomationMode.Disabled.

The issue originates from ItemsControlAutomationPeer. It is reported to Microsoft in their old connect portal here =>

https://connect.microsoft.com/VisualStudio/feedback/details/838165/memory-leak-in-the-itemscontrolautomationpeer-because-items-removed-from-the-itemscollection-are-still-strongly-held-by-the-weakrefelementproxystorage

After certain expand/collapse of RadExpander that is placed inside a floating RadPane the DataContext of the RadExpander is lost

The Docking control must be placed inside DataTemplate.

Also it is possible to reproduce this behavior by executing this process:
  - Load a previously saved layout into the RadDocking control (note that the PanesSource is not set)
  - Set a PanesSource collection. Here the PanesSource objects are correctly added to the control but the previous items from the loaded Layout are not removed.

The PaneHeader is shown and then immediately collapsed. 

Setting the PaneHeader to null can be used as a workaround if the project uses the default theme.

When RadGridView/DataGrid is placed inside a floating Pane and the Docking parent is resized, hovering over the compasses cases a highlight in the GridView/DataGrid

Using the LayoutChangeEnded event to save the layout when docking a floating Pane causes that Pane to not be saved correctly.

When the DragDropMode property is set to Deferred in partial trusted applications a security excpetion is being thrown.

In WPF when show the unpined pane by hovering, when right click to show the contextmenu the pane collapses.

Create content control and change the content in it -when the content contains RadDock the WPF window lose focus.

The XAML team has recently reviewed this issue and will not be addressing it as at this time the team is focusing on the bugs impacting the highest number of developers. If you have encountered this issue and it is blocking for your work please contact us through the support ticketing system with details on your setup and a reference to this item.