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

Memory hogs using the booru browser #38

Closed
NamcoPro opened this issue Apr 13, 2016 · 2 comments
Closed

Memory hogs using the booru browser #38

NamcoPro opened this issue Apr 13, 2016 · 2 comments

Comments

@NamcoPro
Copy link

The tags listed a little over 700 images, I scrolled down to the bottom and used the save images option. It plowed through all 8GB of RAM and the 8GB of extra swap space. This is with a relatively small amount of images, I can't imagine what would happen with very popular tags. I guess this isn't a common scenario, but I bet others save most images and then delete the ones they dislike.

This is also probably on my end, but browsing a directory with lots of images takes some time to startup, other viewers have no problem opening up an individual image in the unsorted mess.

@ahodesuka
Copy link
Owner

The issue when saving a large number of images should be easily fixable.

The load times when opening a directory with a large number of images I'll have to look into.
Around how many images or files are in the directory?

@NamcoPro
Copy link
Author

The directory in question has over 18k files. I tried one with around half of it and the issue is still there albeit not as severe.

ahodesuka added a commit that referenced this issue Nov 27, 2017
Large local image lists now load much faster and thumbnails are
intelligently loaded in order even after the selected image changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants