• Welcome to the Chevereto User Community!

    Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.

    Please keep in mind:

    • This community is user-driven. Always be polite and respectful to others.
    • Support development by purchasing a Chevereto license, which also gives you priority support.
    • Go further by joining the Community Subscription for even faster response times and to help sustain this space
  • Chevereto Support CLST

    Support response

    Support checklist

    • Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
    • Confirm that the server meets the System Requirements
    • Check for any available Hotfix - your issue could be already reported/fixed
    • Read documentation - It will be required to Debug and understand Errors for a faster support response

Website still crashes browser while adding big list of images

Status
Not open for further replies.
lovedigit

lovedigit

👽 Chevereto Freak
Hello,

I know a fix has been implemented with the latest version of chevereto that deals with the browser being crashed while trying to add huge list of high resolution images for upload. It works with considerable number of images, but after a certain amount it still crashes the browser window.

I have 1GB Ram on my server of which only 300MB is being used at any time.
Also, my computer has 8GB Ram. So, I don't think it has to do with the insufficient RAM on either of the machine.
I monitored the CPU usage while adding the images and there were neglegible spike.

If you want I can send you the zip file of images that I am trying to upload to reproduce this error. I would like to mention that it is a NSFW content. So, let me know if you still want it.
 
First of all, queue handling has nothing to do with server hardware. Queue handling happens in your browser, which is a sub-process with limited memory allocation in your computer.

True, v3.7.5 highly improved memory handling in large queues (to be honest, I can't figure a way to optimize it more) but that doesn't mean that you can put an unlimited amount of large images on top of it. Image it as a "car", you won't load a small car with the same load as a truck isn't?. Depending in your computer specs, free memory at that time, threads, etc. you will be able to upload 100 huge images or just 10 of them.

Main problem here is the live preview and image edit, which needs to store the actual images in the browser memory. When you add lets say 100 MB of large images you are actually allocating 1.8-2X that in RAM.

Also, in JavaScript you can't see how many RAM is available or how much CPU is left. It is impossible to guess if in a given machine the thing will hang or not, I can count the MB being allocated to the queue and try to guess how much is being allocated to the RAM, but I can't tell how much machine is available.
 
So, I can't upload it on a chevereto website all at once?
I think Imgur faced the similar issue on their website. The solution they came up with is to remove thumbnail preview for large queue altogether.

See the same queue on Imgur
fT7qeFe.jpg


No disrespect @Rodolfo. I really appreciate your work but this is an issue with the script. 🙂 I am open for any decision you make. Just wanted to bring it in the spotlight to enhance our script.
 
Our editor works before the upload process and I won't change the uploader process at this time. I can't just remove the thumb and pre-upload editor and mostly, I don't want to expend time on this because is common sense. You don't load a car with 10 tons and expect that nothing will go wrong. I don't use After Effects while in the other Window I have a game running at 4K.
 
Last edited:
I didn't come across any other image hosting a website with this issue. Thought Chevereto shouldn't have any issues dealing with a large number of images. I have uploaded 3000 images on Imgur at once without a sweat. Why can't we have such a robust system on chevereto?

If this is how you want it to work, then it's alright. I can live with that. I will just wait for others to face the same issue and let them report it over time to make it significant. I thought this version was dedicated to fixing these very issues, hence, I reported it. 🙂 I don't have any problem with it working the way it does right now. Got a mail from one of my users, and I thought I should forward it here. Cheers!
 
Status
Not open for further replies.
Back
Top