Approved
Last Updated: 31 Oct 2018 08:06 by ADMIN
ADMIN
Boby
Created on: 15 Sep 2016 06:09
Category: RichTextBox
Type: Bug Report
1
RichTextBox: OutOfMemoryException when exporting document containing big image as watermark or in header/footer to PDF
Watermark is drawn for each page in the RadDocument. When the watermark is a larger image, an OutOfMemoryException might occur during export to PDF. The same applies for images in header/footer.
4 comments
ADMIN
Tanya
Posted on: 20 Jul 2018 06:26
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
Patrick
Posted on: 11 Jul 2018 18:50
Hi, I have the same issue. I used RichTextBox since over 6 years now and there is always memory leak in different places in the control depending the version. Sometimes in control menu, other times in the control itself and often, when dealing with pictures. The most frustrating thing is, each time I create a ticket about that, Telerik always ask me a project where I must point where the problem is. I don't know where it is and it's the reason why I ask it!
ADMIN
Boby
Posted on: 05 Apr 2018 08:35
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.
Bernd
Posted on: 06 Jul 2017 12:02
Getting an Out Of Memory Exception is very painful and not acceptable for PCs today if there is no endless loop which generates it.
I'm not talking that is will take time to generate a PDF which is big like 100 pages or more - that's something my customers can understand - but having not enough memory !
Please change it ASAP.
Thanks Bernd
(R&D Manager AMPLECTOR Engineering Germany)