You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, ExtractorData stores all data of the rar file in memory, and when extract() is called, each files inside are also kept in memory as Uint8Arrayextraction property.
This works fine for small rar file, but would run out of memory for big file.
Would you consider adding another Extractor that supports ReadableStream, both for the rar file, and the files inside it?
The text was updated successfully, but these errors were encountered:
It's hard since the Extractor is just a simple wrapper for the file writing API for unrarLib. So technically the unrarlib may not write the file sequentially is hard to rewrite to a streaming class.
Currently,
ExtractorData
stores all data of the rar file in memory, and whenextract()
is called, each files inside are also kept in memory asUint8Array
extraction
property.This works fine for small rar file, but would run out of memory for big file.
Would you consider adding another Extractor that supports
ReadableStream
, both for the rar file, and the files inside it?The text was updated successfully, but these errors were encountered: