Releasing LoadImage memory under MAX 1.14
BlitzMax Forums/BlitzMax Beginners Area/Releasing LoadImage memory under MAX 1.14
| ||
Under BlitzMax 1.14, I had to add :TImage to the line to load an image. However, now my Release command no longer works. The error message is "Subexpression for release must be an integer variable"
Local MyImage:TImage=LoadImage("MyPicture.bmp")
Release MyImage
Now, I know that BlitzMax has its own memory cleanup no but how do I free up the memory correctly now (without BlitzMax own cleanup)? Sin |
| ||
| When using release, you weren't freeing the image but the "pointer" to the TImage (that has to be freed using release, when you use an INT to reference an object like TImage. When you use a TImage there's no need to use release) The image was freed up by BMax's Garbage Collector, and so will be now. When MyImage goes out of scope or is referencing Null or another image, MyPicture will be freed up. |
| ||
| In other words, don't try releasing objects and let BMax worry about managing resources. After all, that's the whole point of having automatic garbage collection. |
| ||
| Thanks. Thats what I thought, but wanted to make sure (as otherwise it would be a memory leak). Hmmm, not sure I like relaying on automatic memory handling though. Cheers. Sin |
| ||
| You can always "Use GCSetMode to enable/disable automatic GC. To perform a manual GC, use GCCollect". (taken from releasenotes.doc) or force a collect using GCCollect. |
| ||
| You can always "Use GCSetMode to enable/disable automatic GC. To perform a manual GC, use GCCollect". (taken from releasenotes.doc) or force a collect using GCCollect. (after NULLing the object) |
| ||
| This doesn't change anything. You still don't free it manually. The GCCollect is just the command to force the garbage collector to collect unused ressources. Its still not freed but pooled for further usage. |
| ||
| Its still not freed but pooled for further usage. Hmmm.. Are we sure this happens? If so, running GCMemalloced should only show increasing or stable mem usage unless you mean BlitzMax keeps the pool seperate to the application. If *that* is true then I don't see how the .exe also shows lowering memusage. You'll notice that it reports lower usage in this example gcmemalloced as if memory *IS* being freed. <edit> I reserve the right to have completely misunderstood. |
| ||
| If the GC just continued to horde memory, what would be the point of it's existence? Also, does it still collect garbage when no one is around? |
| ||
| If I understand you correctly, in auto mode, it does I won't continue to horde memory if you don't, because already allocated memory will be used next time you call your loadimage -or whatever-. Tonyg, have you checked the app with an external memory usage monitor (like taskmgr in Windows 2K/XP)? just to be sure if it really frees memory or allocates it somewhere else or something. (I'd do it but I'm at work now) |
| ||
| Hmmm.. taskmanager reports a higher, stable figure. I guess BlitzMax does have a 'memory currently in use' (gcmemalloced) and memory 'stored' for use (figure shown in taskmanager). |
   |