Its all point-of-view. As far as the user, the OS and the system is
concerned, any app that continues to allocate RAM and does not
return the RAM to the system is a leak in that it drains the system
of its available RAM resource. The app leaks by losing track of and
not returning used RAM to the OS, like borrowing $5 every day from a
friend and never pays it back - such a person would be a leak to
their friends wallet. Another example - a leaky toilet does not
absorb the water, it drains the tank.
If I recall, setting a picture on a canvas leaked back then. Setup a
loop to cycle between two pictures on a canvas. I was trying to
create a winking eye effect with two pictures and a timer. The larger
the pictures and the shorter the period, the faster the leak.
Have fun taking your leaks!
:-)
Gary
On Nov 30, 2007, at 7:12 AM, Eric Richards wrote:
> Hi -
>
> With the talk of memory leak on the nug I was thinking,
> wouldn't a more accurate term be memory absorption ?
>
> When someone says " my app has a memory leak"
> what comes to mind is there app is losing or has less
> memory being used, not more.
>
> This might sound strange, but does anyone
> have an example that would show a "memory leak"
> that works on Rb 5.5.5 and OS 9 ?
>
> I just want to see for my self, first hand experience.
>
> Thanks
>
> Eric
>
> _______________________________________________
> Unsubscribe or switch delivery mode:
> <http://www.realsoftware.com/support/listmanager/>
>
> Search the archives:
> <http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|