Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Very large memory being used for a 50mb excel file

See original GitHub issue

When I make the call to ExcelReaderFactory.CreateReader(Stream stream), which stream contains the contents to a 50mb excel file - a total of 800 mb gets eaten up by that call (halting execution while doing so).

Is this using DOM? I thought only a single element/line was ever loaded at a time in the memory.

Issue Analytics

State:
Created 2 years ago
Reactions:1
Comments:27

Top GitHub Comments

1reaction

appel1commented, May 14, 2021

The Server GC trades memory in favor of throughput. Then there’s the Retain VM option that also affects how .NET frees memory back to the OS.

I have an idea how we can change ExcelDataReader to allocate less but will have to test if it has any real world impact. Could be that the objects we can do something about are so shortlived that it doesn’t matter.

0reactions

ArjunVachhanicommented, Aug 19, 2023

@kikaragyozov I am also facing memory issue when upload huge files. In my case files are more than 200MB in size.

So I have decided to a build a library to read huge Xlsx file. library is mostly ready. If you try it today it should work fine. please fell free to try and share your feedbacks and bugs. In coming days I will push few more changes to iron out any issue and add documentation.

Link to repository https://github.com/ArjunVachhani/XlsxHelper