Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An error occurred when generating Blob object. #301

Open
Triramama opened this issue Aug 29, 2024 · 3 comments
Open

An error occurred when generating Blob object. #301

Triramama opened this issue Aug 29, 2024 · 3 comments

Comments

@Triramama
Copy link

i spent a lot of time pulling 500 images and this thing won't give them to me, wtf
image

@ccloli
Copy link
Owner

ccloli commented Aug 29, 2024

See README.md.

In a short, you're downloading a gallery that's too large and the browser cannot handle it. That's the limit of your browser (and your system if you don't have too much RAM).

There should be a warning popup before you downloading a gallery that's larger than 300 MB, and for best practice, never download a gallery larger than 500 MB.

For large gallery I'd recommend using torrents for free if available, or offical archiver by spending a few GPs, or tools that doesn't rely on browser like gallery-dl.

@Triramama
Copy link
Author

i have 64gb of ram on my pc ffs and i can't find any information on firefox limiting ram, nice headcanon

@ccloli
Copy link
Owner

ccloli commented Aug 30, 2024

I'd say Firefox is somehow tricky. Around 9 years ago when the script comes out, sometimes Firefox will pass but sometimes it throws out of memory error, and a possible way is using browser's advanced GC function, where you can still find it here.

But I checked your case just now, it seems that the 2 GB hard limit is the same as Chrome (or say it would probably be Chrome copied Firefox, since Chrome only have 500 MB years ago). I'm not sure if it's a standard, but at least it's a browser side limit.

At that time, there's a way to bypass such limit is FileSystem API, which should be a standard but removed years ago, and now becomes Chrome-only API. So if you're using browsers not based on Chromium, you're out of luck. There're new ways to fix it like the tricky Services Worker + Streams (#226), or the Chrome-only-for-now File System Access API, but for now I've no plan to implement them.

Duplicated with #252 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants