Unplanned
Last Updated: 31 Oct 2018 07:53 by ADMIN
ADMIN
Tanya
Created on: 27 Nov 2015 17:31
Category: RichTextBox
Type: Bug Report
3
RichTextBox: Memory leak related to DelayedExecution internal class when editing RadDocument
The memory leak is reproducible when the main thread is too busy to dispose objects used by RadDocument internally. Thus, the RadDocument instances are kept alive in the memory. 

Workaround: When the scenario includes back processing of documents: Start different threads responsible to perform the required operations and use the following code:

Dispatcher dispatcher = Dispatcher.CurrentDispatcher;
dispatcher.BeginInvokeShutdown(DispatcherPriority.Normal);
Dispatcher.Run();

anywhere in the background thread processing the RadDocument.
0 comments