I have this textbox that a print to an image. Then, after it is done I blit the textbox onto screen. Then I free that image and we'd think everything to be a-cool.
But when I look at my memory usage, while that textbox is on screen, the memory used for verge skyrockets at a rate of 3megs/s, for each textbox on screen, and eventually the game become a big mess.
So i guess I have problems using FreeImage.
Here is what I did, in pseudo code.
start
declare boxImg;
loop
boxImg = newimage;
do thing with boxImg;
blit boxImg on screen;
freeImage boxImg;
showpage
end loop
end

Thanks for your help!

Well, i tried a lot of things, and eventually I kept only the load image and freeImage, and though it took less memory, still it's growing at around 700k/s


void textbox(int x, int y, int x2, int y2)
{
int widthBox = x2 - x;
int heightBox = y2 - y;
int boxImg = NewImage (widthBox, heightBox);
FreeImage(boxImg);
}


textbox(), of course, being called in a loop.

if I take the two lines off, like that:

void textbox(int x, int y, int x2, int y2)
{
int widthBox = x2 - x;
int heightBox = y2 - y;
}


then it's allright, it doesn't take any memory at all (duh).

Quote:

What Jesse said is true, sadly. And a bit unnerving. However, memory use should be considerably reduced via this:

(pseudocode)

start

declare boxImg = newimage;

   loop

      do thing with boxImg;

      blit boxImg on screen;

      showpage

   end loop

freeImage boxImg;

end

Look for the simple solution, Shoe-San.

IN DEFENSE OF MY REPUTATION

This is a new bug. CONTRARY TO GAYO IT HAS NOT BEEN BROKEN FOR 2 YEARS. The source code I have on my computer (which is very old) looks like THIS:

void vc_FreeImage()

{	

	int handle = vc->ResolveOperand();

	if (handle == 0)

		vc->vcerr("vc_FreeImage() - cannot free a null image reference!");

	if (handle == 1)

		vc->vcerr("vc_FreeImage() - cannot free the screen reference");

	if (handle<0 || handle>=MAX_IMAGES)

		vc->vcerr("vc_FreeImage() - handle is a bogus reference!");

	if (!imagebay[handle].active)

		vc->vcerr("vc_FreeImage() - there is no allocated image associated with this reference!");

	delete imagebay[handle].ref;

	imagebay[handle].ref = 0;

	imagebay[handle].active = false;

}

NOTE THE SECTION WHERE IT FREES THE IMAGE. I would also point out that in addition to actually freeing the image, it performed a plethora of helpful and useful checks that SOMEONE quite possibly ZEROMUS arbitrarily deleted! Not only is it a functional FreeImage, it is a damned fine FreeImage. AND NOW MY HONOR IS RESTORED AND I GO TO BED.

zzz

We don't need to blame people, but it's fun and makes us feel better about ourselves.

Beware of the south!