Out of memory error on IE11 #167
Labels
No Label
DBF
Dates
Defined Names
Features
Formula
HTML
Images
Infrastructure
Integration
International
ODS
Operations
Performance
PivotTables
Pro
Protection
Read Bug
SSF
SYLK
Style
Write Bug
good first issue
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sheetjs/sheetjs#167
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'm trying to write 40.000 rows by 220 columns into an excel file.
On average only 15 columns per row actually contain a value, the others are empty.
Creating the worksheet already generates a sizeable memory load (seen in task manager and IE's memory profiler) but once I pass it to XLSX.write() the memory consumption goes wild.
Used memory increases very quickly by over 100mb at a time and I soon thereafter receive an out of memory error.
Size of the downloaded spreadsheet should be ~70mb. I've managed to download a spreadsheet with 20.000 rows that is about 35mb.
I know this is kind of vague, please let me know which other details I could provide!
BTW: I can't use another browser because of some other code my project uses.
Best regards,
Timo
EDIT: I've attached a screen clipping to show the sudden increase in memory consumption once the worksheet/workbook gets handed over to XLSX.write()
I'll try to create a reproducible test case and see where the blowup happens. Would you say the data is primarily numeric or textual? A rough estimate of the ratio would help.
Thanks for the quick reply. The data is primarily numeric, I'd estimate the ratio of numbers to text is about 15 to 1. If it would help I could upload a smaller spreadsheet (20.000 rows) with less data that I managed to generate without running into the out of memory error.
Hi there, I'm wondering if you've had any time to look into the issue and run a test? We're still experiencing the same issue and its effectively blocking us from creating large spreadsheets.
I've tried to modify (read: hack) the code so that an array of arrays can be passed into the library as I assumed that high memory consumption was due to a lot of cell objects being created. It doesn't seem to make a big difference at the moment.