CODEWITHSUNDEEP
image-processingjava-meloadingsprite
fixmycode
fixmycode

Reputation: 8506

Loading Images in J2ME?

I'm not so new to the concepts present on J2ME, but I'm sort of lazy in ways I shouldn't: Lately my app has been loading images into memory as they were candy...

Sprite example = new Sprite(Image.createImage("/images/example.png"), w, h);

and I'm not really sure it's the best way, but it worked fine in my Motorola Z6, until last night, when I tested the app in a old Samsung cellphone and the images wont even load and require several attemps of starting the thread to show up. The screen was left on white, so I realized that it has to be something about Image loading that I'm not doing quite well... Is there anyone who can tell me how to properly make a loading routine in my app?.

Upvotes: 2

Views: 2010

Answers (3)

Fostah
Fostah

Reputation: 11776

I'm not sure exactly what you are looking for, but the behavior you describe very much sounds like you are experiencing an OutOfMemory exception. Try reducing the dimensions of your images (heap usage is based on dimension) and see if the behavior ceases. This will let you know if it is truly an OutOfMemory issue or something else.

Other tips:

  1. Load images largest to smallest. This helps with heap fragmentation and allows the largest heap space for the largest images.
  2. Unload (set to null) in reverse order of how you loaded and garbage collect after doing so. Make sure to Thread.yield() after you call the GC.
  3. Make sure you only load the images that you need. Unload images from a state that the application is no longer in.
  4. Since you are creating sprites you may have multiple sprites for one image. Consider creating an image pool to make sure you only load the image once. Then just point each Sprite object to the image within the pool that it requires. Your example in your question seems like you would more than likely load the same image into memory more than once. That's wasteful and could be part of the OutOfMemory issue.

Upvotes: 4

Fred Grott
Fred Grott

Reputation: 3476

Using a film image(a set of images by a defined dimension in one image) and use logic to pull them out one at a time.

Because they a grouped into one image, you are saving header space per image and thus can reduce the memory used.

This techniques was first used in MIDP 1.0 memory constrained devices.

Upvotes: 1

fixmycode
fixmycode

Reputation: 8506

Using the Fostah approach of not loading images over and over, I made the following class:

public class ImageLoader {
    private static Hashtable pool = new Hashtable();

    public static Image getSprite(String source){
        if(pool.get(source) != null) return (Image) pool.get(source);
        try {
            Image temp = Image.createImage(source);
            pool.put(source, temp);
            return temp;
        } catch (IOException e){
            System.err.println("Error al cargar la imagen en "+source+": "+e.getMessage());
        }
        return null;
    }
}

So, whenever I need an image I first ask the pool for it, or just load it into the pool.

Upvotes: 0

Related Questions