Due to excessive memory consumption when decoding images, OutOfMemoryException can be thrown when viewing documents with large images inside them. 

Workarounds: 
- Set ExtensibilityManager.MaxImageSize = null. This will skip one resizing step, and could be beneficial in documents containing few large images.
- Use 64-bit process for the client application. This allows the process to consume much more memory. Note that starting 64-bit process while debugging can be tricky, as described in this blog post: https://weblog.west-wind.com/posts/2016/Dec/19/Visual-Studio-Debugging-and-64-Bit-NET-Applications.

Available in R1 2018 Official release version.

QueryableEntityCoreCollectionView internal collections not in sync.

Currently, there is no workaround to this behavior.

When a chart have long labels on the X axis (like date and time) the zoom is not accurate on the horizontal extents with both mouse wheel and drag area.

The reason is probably that the screen coordinates of the selected area are not mapped correctly on the X axis. The mapping works fine for tooltip.

You can verify this behavior in the attached Solution. In the images you can see the selected area (01), that the zoomed area is a region with no points (02) and the actual position of the points.

When using StyleManager.Theme to set a theme for the control, the scroll does not get themed. When setting the theme for the whole application, the scroll is themed correctly. 

To work this around, subscribe to the Loaded event of the RadChat control. Using the visual tree helpers, get the ScrollBar element with x:Name="PART_VerticalScrollBar" and set the theme for it using the StyleManager.SetTheme static method.

Labels (instances of the LightTextBlock control) remain on the render surface after the ItemsSource is replaced dynamically and the row or column count is changed. As a workaround, the control can be redrawn manually to clear the surface:

        var temp = heatmapTest.Template;
        heatmapTest.Template = null;
        heatmapTest.Template = temp;

When a RadGridView cell has a validation error, a red border will appear around the cell. In this case, the top validation border is missing on the first row cells. As a workaround, you can move the ContentPresenters of the cells a little bit in the loaded event of the control.

private void RadGridViewView_Loaded(object sender, System.Windows.RoutedEventArgs e)
{
    var treeListView = sender as RadTreeListView;
    var editorPresenters = treeListView.ChildrenOfType<ContentControl>().Where(x => x.Name == "PART_ContentPresenter" && x.ParentOfType<GridViewCell>() != null);
    foreach (var item in editorPresenters)
    {
        item.Margin = new System.Windows.Thickness(1);
    }
}

In AgendaView, you can see the start, end, and subject of each appointment. When All Day event is set to one appointment, its start and end time is not changed. The text can be changed to All Day Event.

When using LineHighlightTagger a NullReferenceException is thrown. To workaround this exception, you can add a custom TextFormatDefinition object to the TextFormatDefinitions collection of the RadSyntaxEditor.

this.syntaxEditor.TextFormatDefinitions.AddLast(LineHighlightTagger.LineHighlightFormatDefinition, new TextFormatDefinition(new Telerik.Windows.Controls.SyntaxEditor.UI.Pen(new SolidColorBrush(Colors.Gray), new Thickness(1))));

The WorkbookContentChanged event is invoked right after importing a document. 

The rendering of the image is not fully parsed and the next attribute cannot be properly read. 

System.InvalidCastException: 'Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfArray' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfInt'.'

Per the thread at "http://www.telerik.com/forums/isexpandablebinding-requires-user-interaction-with-control-to-take-effect" I have modified the IsExpandedRowBinding sample to recreate the problem. I modified the button to expand and collapse the first row. To reproduce the problem:

1. Expand the first row.
2. Scroll down so the first row is not visible but it's children are visible.
3. Press the button. The expected behavior is the first row should collapse but nothing happens.
4. Scroll up so the first row is visible. The first row collapses.