Full Games List
Featured Games
New Games
Reviews
Images
Blogs
Game Updates
Images Feedback Summary
Game Design Highlights
Tutorials
Articles
Scripts
Utilities / Plugins
Resources
Engines
Engine Bulletins
What is Makerscore?
Past Events
Achievements
Forums
Post History
Chat
New to RMN?
Full Store List
RMN Music Pack (free)
Add Review
Subscribe
Nominate
Submit Media
RSS
WolfCoder- Added: 01/20/2011 02:45 PM
- Last updated: 04/25/2024 04:00 PM
- 3689 views
Posts 
Pages:
1
View playlists
Close
WolfCoder
3554
Yes. The engine composes a text out of strings and pictures to display more complicated things and it stores all the results of an input string into memory. Almost every object like this is allocated on the heap via new and delete so if I make a mistake it will leak every time you see a dialog box.
Thankfully, I've checked and detected no leaks.
Thankfully, I've checked and detected no leaks.
EnderX
562
If you want to google it, your call. However, if not, or for others who come by, simple explanation ahead.
Computers have only so much available RAM (Random Access Memory) for programs to run in. A program allocates some of that memory from this 'available memory pool' each time it needs some, and then supposedly releases the memory when it's finished with whatever it needed it for, returning it to the pool.
A Memory Leak occurs when the allocated memory isn't needed for anything else, but the program fails to properly release/return it. After this happens several times, a fair amount of RAM can be 'eaten' by such unneeded-but-held items...which means there's less available for everything else to use. In effect, some of the available RAM has effectively 'leaked out' of the pool of available RAM.
Computers have only so much available RAM (Random Access Memory) for programs to run in. A program allocates some of that memory from this 'available memory pool' each time it needs some, and then supposedly releases the memory when it's finished with whatever it needed it for, returning it to the pool.
A Memory Leak occurs when the allocated memory isn't needed for anything else, but the program fails to properly release/return it. After this happens several times, a fair amount of RAM can be 'eaten' by such unneeded-but-held items...which means there's less available for everything else to use. In effect, some of the available RAM has effectively 'leaked out' of the pool of available RAM.
author=EnderX
If you want to google it, your call. However, if not, or for others who come by, simple explanation ahead.
Computers have only so much available RAM (Random Access Memory) for programs to run in. A program allocates some of that memory from this 'available memory pool' each time it needs some, and then supposedly releases the memory when it's finished with whatever it needed it for, returning it to the pool.
A Memory Leak occurs when the allocated memory isn't needed for anything else, but the program fails to properly release/return it. After this happens several times, a fair amount of RAM can be 'eaten' by such unneeded-but-held items...which means there's less available for everything else to use. In effect, some of the available RAM has effectively 'leaked out' of the pool of available RAM.
OK. Thanks for that.
WolfCoder
3554
If there was a memory leak, it means the program will eventually crash as you go through dialog boxes. So I check for these problems now so that I don't have to hunt it down much further down the road.
WolfCoder
3554
Aaa I was thinking of doing more tomorrow but I'll think I'll finish more of the escape commands and scrolling since I got bored of shooting floating robots with an anti material rifle.
Radnen
1806
But the memory leaks you're talking about would very tiny.
But because textboxes are used so frequently... Yeah.
But because textboxes are used so frequently... Yeah.
WolfCoder
3554
A memory leak of one byte is unacceptable though, I want to keep the mysterious random bugs to a minimum.
Pages:
1
