Hi Patrick,

Indeed, memory issues are usually hard to reproduce and can be observed in specific scenarios with a particular setup. RadRichTextBox is a control coming with a lot of features and different possibilities so it can be used in various scenarios. That is why we need your help to replicate the issue on our end so we can try to suggest you a workaround or at least add the problem to our backlog for fixing in the future. I encourage you to contact the support team as I believe they will do their best to assist in the difficulties you are experiencing.

Regards,
Tanya

Hello Bernd, I believe the team addressed your specific use case to a greater extent in our private conversations using support tickets, but I still want to address the comment here. 

From our components vendor perspective, our code is working in a “foreign” process, a process which can have arbitrary memory consumption. In the border case, a developer may try to load our components in a process which has already exhausted all of the available memory (which is less than 2GB for a 32-bit process), and in this case the OutOfMemoryException will be imminent. 

Of course this is not excuse for this particular case, in which we currently think that we can employ some images caching mechanism to optimize the scenario. Make sure to follow the item in order to get notified on potential status changes.