Image downloads fails with "failure inside handle_image_callback, out of memory in graphics memory pool"

I got error reports from my users about my audio provider getting stuck during download, and after digging into it, it seems likely that it's the image download that fails.
Creating a similar case as the users (long playlist, over 20 items, all with unique images), I get the following error in the simulator towards the end of the sync (ie downloading some of the last images):

Error: System Error
Details: failed inside handle_image_callback
Exception: The requested memory could not be allocated from the graphics memory pool

Is there anything I can do to detect this. I'm fine with just ignoring further images if it fails, but I already have a try/catch around the makeImageRequest, and it's not catching this, seems like the system just goes straight to crashing.

The only options I see at the moment is to reduce the size of the images. The largest images are 256x256 on amoled screens (the crashing device in the report is an Epix), or just limit the number of images I download / the size of the playlist.

0 flocsy🤠 8 months ago

Why are you loading the images to the graphic pool

Is it not enough to save them

0 Andreas Tarandi 8 months ago in reply to flocsy🤠

I'm not intentionally doing that, but I get back a BitmapReference from makeImageRequest, like this:

	Communications.makeImageRequest(url, null,
			{
				:maxWidth => width,
				:maxHeight => height,
				:packingFormat => Communications.PACKING_FORMAT_JPG
			}, self.method(:onImageResponse));

0 flocsy🤠 8 months ago in reply to Andreas Tarandi

And I suppose you are freeing your variable, but it is not being freed from the graphic pool

0 Andreas Tarandi 8 months ago in reply to flocsy🤠

I do keep the image in a dictionary, to be able to store it in my Storage for later. But maybe I could convert it to some other format to not keep it in the graphics pool, and store that in my playlist in Storage.

I haven't found any documentation on how to deal with the various bitmap types, so I'm not clear on if I need to explicitly free the bitmap references too, or if it's garbage collected.

I found that even if I did release all handles to the images, I had to restart the emulator for the graphics pool to free up.