Load and scale image

10 posts / 0 new

Last post

Wed, 2016-03-23 04:04

mritter0

Offline

Last seen: 2 years 7 months ago

Joined: 2014-04-21 21:15

Load and scale image

In my program I load and scale 20+ images at startup, and potentially dozens more later. I thought I had some nice working code, until I realized the ScaleBM is not being freed and I was losing 1.6MB of RAM.

Load it at startup

ImgObjects[IMG_DEF_DRAWER_16]=LoadImageScale((STRPTR)"ENVARC:Sys/def_drawer.info",20,18,FALSE,TRUE,FALSE);

Free image when quit

DisposeImage(ImgObjects[IMG_DEF_DRAWER_16]);

The code below is a stripped out version of how I load and make an image into a BitMapClass object

Object *
LoadImageScale(STRPTR Path,uint32 w,uint32 h,BOOL UpScale,BOOL KeepAspect,BOOL HalfAlpha)
{
	Object							*DTO, *Img;
	struct BitMapHeader				*bmhd=NULL;
	struct BitMap					*OrigBM, *ScaleBM;
	APTR							Lock;
	APTR							Memory;
	uint32							BytesPerRow;
	struct pdtBlitPixelArray		pdtBlitPixelArrayBuffer;
	uint32							ScaleWidth, ScaleHeight;
	float32							ScaleFactorX, ScaleFactorY;
 
	if (!(DTO=IDataTypes->NewDTObject(Path,
		DTA_GroupID,						GID_PICTURE,
		PDTA_Screen,						DefaultPubScreen,
		PDTA_PromoteMask,					TRUE,
		PDTA_DestMode,						PMODE_V43,
	TAG_END)))
	{
		return(NULL);
	}
 
	if (!(OrigBM=IGraphics->AllocBitMapTags(bmhd->bmh_Width,bmhd->bmh_Height,32,
		BMATags_PixelFormat,				PIXF_A8R8G8B8,
		BMATags_Clear,						TRUE,
		BMATags_Displayable,				TRUE,
	TAG_DONE)))
	{
		if (DTO != NULL)
		{
			IDataTypes->DisposeDTObject(DTO);
			DTO=NULL;
		}
 
		return(NULL);
	}
 
// figure out new scaled sizes
 
	if (!(ScaleBM=IGraphics->AllocBitMapTags(ScaleWidth,ScaleHeight,32,
		BMATags_PixelFormat,				PIXF_A8R8G8B8,
//		BMATags_BitmapInvisible,			TRUE,
		BMATags_Clear,						TRUE,
		BMATags_Displayable,				TRUE,
	TAG_DONE)))
	{
		IGraphics->FreeBitMap(OrigBM);
 
		return(NULL);
	}
 
// scale it
 
	IGraphics->FreeBitMap(OrigBM);
 
	if (!(Img=IIntuition->NewObject(BitMapClass,NULL,
		BITMAP_BitMap,						ScaleBM,
		BITMAP_Width,						ScaleWidth,
		BITMAP_Height,						ScaleHeight,
		BITMAP_HasAlpha,					TRUE,
		BITMAP_Screen,						DefaultPubScreen,
		BITMAP_Precision,					PRECISION_EXACT,
		BITMAP_Masking,						TRUE,
	TAG_DONE)))
	{
		IGraphics->FreeBitMap(ScaleBM);
 
		return(NULL);
	}
 
 
// This line is what I need, but can't be here.
// It clears the BitMapClass image.
// It will crash when DisposeImage().
 
	IGraphics->FreeBitMap(ScaleBM);
 
	return(Img);
}
 
 
VOID
DisposeImage(Object *Img)
{
	if (Img != NULL)
	{
		IIntuition->DisposeObject(Img);
		Img=NULL;
	}
}

The ScaleBM is not being freed so losing a lot of RAM.

I don't want to make an array like
struct BitMap *ScaleBM[20];
That is not an option.

How do I fix this?

Wed, 2016-03-23 13:54

thomas

Offline

Last seen: 1 week 5 days ago

Joined: 2011-05-16 14:23

Re: Load and scale image

I don't think that ScaleBM is your problem. It's rather the datatype object. If all goes well you never DisposeDTObject(DTO).

You've already proven that ScaleBM *is* freed by saying that DisposeImage crashes if you free it explicitly.

Wed, 2016-03-23 17:46

mritter0

Offline

Last seen: 2 years 7 months ago

Joined: 2014-04-21 21:15

Re: Load and scale image

I am doing DisposeDTObject(DTO) just didn't show it. Ripped out a bunch of code to make it smaller. Everything works, just not when disposing of the image.

// This line is what I need, but can't be here.
// It clears the BitMapClass image.
// It will crash when DisposeImage().
 
	IGraphics->FreeBitMap(ScaleBM);

This is the problem area. When I do DisposeImage() it is not freeing all the memory for the images (the ScaleBM bitmap). That line can't be there, just showing what the issue is.

When I load and scale the images and quit I lose 1.6MB of RAM. If totally skip the loading/scaling I don't. So it is something with the way I am loading/freeing them.

What would be nice is if the BitMapClass could copy the supplied bitmap and release it's private one when disposed. Like ChooserClass has CNA_CopyText. Then I could IGraphics->FreeBitMap(ScaleBM); right after making the BitMapClass object.

	if (!(Img=IIntuition->NewObject(BitMapClass,NULL,
		BITMAP_CopyBitMap,                                     TRUE,
                BITMAP_BitMap,						ScaleBM,
		BITMAP_Width,						ScaleWidth,
		BITMAP_Height,						ScaleHeight,
		BITMAP_HasAlpha,					TRUE,
		BITMAP_Screen,						DefaultPubScreen,
		BITMAP_Precision,					PRECISION_EXACT,
		BITMAP_Masking,						TRUE,
	TAG_DONE)))
 
        IGraphics->FreeBitMap(ScaleBM);

Problem solved. But, doesn't exist. Hint hint....

Thu, 2016-03-24 13:25

(Reply to #3) #4

salass00

Offline

Last seen: 7 months 2 weeks ago

Joined: 2011-02-03 11:27

Re: Load and scale image

Just make sure you call FreeBitMap(ScaleBM) after you call DisposeObject().

If you don't want to keep track of the bitmap pointer yourself you can just query it with GetAttr() in your DisposeImage() function as BITMAP_BitMap tag supports OM_GET.

Fri, 2016-03-25 04:18

mritter0

Offline

Last seen: 2 years 7 months ago

Joined: 2014-04-21 21:15

Re: Load and scale image

That is working out great! Thanks!

It also helped me track down another issue I was having in a previous post.

Thu, 2018-03-08 00:54

mritter0

Offline

Last seen: 2 years 7 months ago

Joined: 2014-04-21 21:15

Re: Load and scale image

After doing some checking, the memory is still not being freed, even when I

	IIntuition->GetAttrs(Img,
		BITMAP_BitMap,							&BM,
	TAG_DONE);
 
	IIntuition->DisposeObject(Img);
 
	if (BM)
		IGraphics->FreeBitMap(BM);

BroadBlues replied to me on Amigans.net that maybe the images are being cached. The more I think about it, I doubt that they are. Because ever run loses more RAM.

I just don't get why this works/frees correctly

	return(IIntuition->NewObject(BitMapClass,NULL,
		BITMAP_SourceFile,						Render,
		BITMAP_SelectSourceFile,				Select,
		BITMAP_DisabledSourceFile,				Disabled,
		BITMAP_Screen,							DefaultPubScreen,
		BITMAP_Precision,						PRECISION_EXACT,
		BITMAP_Masking,							TRUE,
	TAG_DONE));

but this does not

	if (!(Img=IIntuition->NewObject(BitMapClass,NULL,
		BITMAP_BitMap,							ScaleBM,
		BITMAP_Width,							ScaleWidth,
		BITMAP_Height,							ScaleHeight,
		BITMAP_HasAlpha,						TRUE,
		BITMAP_Screen,							DefaultPubScreen,
		BITMAP_Precision,						PRECISION_EXACT,
		BITMAP_Masking,							TRUE,
	TAG_DONE)))

Did a bug sneak in to the BitMapClass that isn't freeing the object and/or BITMAP_BitMap?

Grabbing at straws now.......

Thu, 2018-03-08 15:47

(Reply to #6) #7

broadblues

Offline

Last seen: 4 years 10 months ago

Joined: 2012-05-02 21:48

Re: Load and scale image

Did a bug sneak in to the BitMapClass that isn't freeing the object and/or BITMAP_BitMap?

You are passing bitmap.image a bitmap. *You* are responsible for freeing it.

I'm doing just this in a context where I generate cached text images, I delete my own bitmaps (after I dispose of the bitmap.image naturally).

BTW you do realise that bitmap.image will load the datatype image and scale if for you? No need for the dedicated datatypes load and ScaleBM step.

[edit]
Reading the thread again you probably are aware that you need to free the bitmap yourself.

Futher thinking you realise that the bitmap data is in video ram? (unless you very specifically set it as BMF_PRIVATE, but that wouldn't display properly. So losing 1.6 Mb of main ram is not goinf to be because of the bitmap.

1.6Mb is not very much, it could be from memory fragmentation, rather than any real loss. How are you measuring this loss?

Do you use direct calls to AllocVecTags() or do you have wrapper function? Have you got any kind of memory allocation / freeing tracking? This would show up anything you didn't release at prgram quit.

Eg in MultiViewer / MultiEdit I have a alternate set of memory code that will print out any unfreed memory at exit and tell me where I allocated it.

I only compile this in whilst testing, recompiling for release.

Fri, 2018-03-09 01:30

mritter0

Offline

Last seen: 2 years 7 months ago

Joined: 2014-04-21 21:15

Re: Load and scale image

VOID
DisposeImage(Object *Img)
{
	struct BitMap					*BM=NULL;
 
	if (Img==NULL)
		return;
 
	IIntuition->GetAttrs(Img,
		BITMAP_BitMap,							&BM,
	TAG_DONE);
 
	IIntuition->DisposeObject(Img);
 
	if (BM)
		IGraphics->FreeBitMap(BM);
}

I am freeing the bitmap after I dispose of the BitMapClass object like salass00 said to do. I put in some Printf()'s to make sure it was actually doing the FreeBitMap() call.

Workbench Explorer loads 50+ AISS images at start up. It is up to 2MB+ RAM loss now. I use both loading methods because I do some manipulation to several of the images. And use IconClass for loading icon images (the icon datatype isn't 100% and not installed by default).

To test for memory loss I disable loading with my custom code. Avail. Run. Quit. Avail. Not much loss.
Do opposite, enable my code, disable simple BitMapClass (no manipulation, straight loading) loading (maybe 15 images). Avail. Run. Quit. Avail. 2MB+ memory loss.

If I browse some drawers, more RAM is lost, like 3MB total.

I have made sure the
if (!(DTO=IDataTypes->NewDTObject(Path,
is freed.

Using AllocVecTags() and AllocBitMapTags(). No weird custom wrappers.

I am at a loss. Everything looks right, does all the steps, just won't free the memory.

Fri, 2018-03-09 02:38

(Reply to #8) #9

broadblues

Offline

Last seen: 4 years 10 months ago

Joined: 2012-05-02 21:48

Re: Load and scale image

Avail. Run. Quit. Avail. 2MB+ memory loss.

This not a reliable method on AmigaOS 4, there caches and many different ways that memory may not be returned to the system until the system runs really short of memory and calls the various memory release hooks (forget the proper name for them just at the moment).

The memory might be cached by the datatypes system, it might be cached in the filesystem, or any of a number of options.

I wouldn't worry.

Sat, 2018-03-10 02:56

#10

mritter0

Offline

Last seen: 2 years 7 months ago

Joined: 2014-04-21 21:15

Re: Load and scale image

I have worked on and walked away from this several times in the last 2 years. Walking away again.

On my X5000 with 2GB RAM it's not big deal. But in WinUAE and real A1200 with 128MB RAM, there isn't much left to lose.

Search form

User login