Home/ Questions/Q 6603109
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T18:57:50+00:00

I’m using simple objects to wrap Image objects and track when they are loaded,

  • 0

I’m using simple objects to wrap Image objects and track when they are loaded, like so:

var preloader = {
    loaded: false,
    image: new Image()
}
preloader.image.onload = function() {
    preloader.loaded = true;
}
preloader.image.src = 'http://www.example.com/image.jpg';

When the image is finished loading, preloader.loaded is set to true. That all works fine.

My question is, what happens when I have so many of these objects and so many images that the browser cache is used up. Eventually once enough images are loaded, the browser will start to dump older ones out of the cache. In that case won’t I end up with JavaScript objects where loaded=true, but the image file is not actually cached anymore?

This is hard to test, because I can’t tell at any given point which images are still in the cache and which aren’t.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Once you’ve loaded the image from a web page, it’s not being used from the cache. It’s actually in the browser page memory for the duration of the browser page lifetime or until you get rid of this JS object so it can be garbage collected.

    The cache is not used for storage of loaded images on a page. The cache is used so that the next time a load of this image is requested, it can be loaded much faster. If you load so many images that it exceeds the storage of the cache, nothing will happen to the images you have already loaded as they are in browser memory for the duration of the page (independent of the cache). What will happen is that some of the images you loaded will no longer be in the cache so the next time some browser pages wants to load them, they won’t be in the cache and will have to be fetched from their original web-site over the internet.

    • 0