This is a migrated thread and some comments may be shown as answers.

Excel File Export - OutOfMemoryException

11 Answers 397 Views

Spreadsheet

This is a migrated thread and some comments may be shown as answers.

Siward Land asked on 03 Dec 2013, 07:08 PM

I am using the below code to create an excel file:



Workbook workbook = new Workbook();

workbook.Worksheets.Add();

string fileName = "SampleFile.xlsx";

IWorkbookFormatProvider formatProvider = new XlsxFormatProvider();

using (FileStream output = new FileStream(fileName, FileMode.Create))

{

formatProvider.Export(workbook, output); //System.OutOfMemoryException thrown here

}

Where the variable workbook contains a lot of data (about 115000 rows worth). My problem is that the host computer doesn't have enough memory to do the excel export, so an outofmemoryexception is thrown at formatProvider.export().

Is there a way to split up Excel file export into smaller parts so that I don't run out of memory? I need all of the data to be in the same excel file.

Siward

11 Answers, 1 is accepted

answered on 04 Dec 2013, 11:47 AM

Hi Siward,

This issue is fixed already and the fix will be included in the Q3 2013 SP1 release. However there is another known problem with our Zip library that does not allow exporting large documents. We are working on resolving this and we expect to be able to release the fix for Q1 2014.

I am sorry for the inconvenience. Please, let me know if you have any further questions.

Regards,
Nikolay Demirev
Telerik

TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>

answered on 29 Apr 2015, 11:48 AM

Hi Dean,

In the past releases we have introduced plenty of performance and memory improvements, as well as new functionality for the Spreadsheet and SpreadProcessing components.

I took a look at the ticket you mentioned and just wanted to elaborate that the SpreadProcessing library is basically shared between the WPF and ASP.NET AJAX suites. It also looks to me you are actually using the most recent version of the library - Q1 2015 in which case I am afraid we have no suggestions additional to the ones Konstantin already provided - retrieve the data from the database directly instead of using RadGrid or limit the amount of data you are exporting.

Regards,
Petya
Telerik

See What's Next in App Development. Register for TelerikNEXT.