Ultrashock Forums - View Single Post

sentinels · 2008-11-20 #2

one thing i've learned in all my years of dev (and especially since picking up C/Objective-C again) is you can not rely on other things to handle garbage collection/memory management for you. you must, i repeat: must, handle your own memory management. make sure bitmaps are being disposed of properly (look at the BitmapData dispose() method). make sure all your listeners are removed upon being removed from the display list and prior to it being killed. null out objects after you remove your listeners on it to ensure that the object is flagged for deletion. there are a lot of other things you should watch out for and i'm sure you can go through your app and find many places where this is not being handled. especially if you're using an outside framework other than your own.

	sentinels	2008-11-20 #2
	one thing i've learned in all my years of dev (and especially since picking up C/Objective-C again) is you can not rely on other things to handle garbage collection/memory management for you. you must, i repeat: must, handle your own memory management. make sure bitmaps are being disposed of properly (look at the BitmapData dispose() method). make sure all your listeners are removed upon being removed from the display list and prior to it being killed. null out objects after you remove your listeners on it to ensure that the object is flagged for deletion. there are a lot of other things you should watch out for and i'm sure you can go through your app and find many places where this is not being handled. especially if you're using an outside framework other than your own.