http://blogs.msdn.com/shawnhar/archive/2007/07/09/delegates-events-and-garbage.aspxSome commenters on my previous post asked for more information about the situations where delegates allocate memory. Here's the scoop. There are actually three reasons why careless use of delegates or events can cause memory allocations: Allocating delegateenCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/shawnhar/archive/2007/07/09/delegates-events-and-garbage.aspx#3790960Tue, 10 Jul 2007 05:54:36 GMT91d46819-8472-40ad-a661-2c78acb4018c:3790960snprbob86<p>RE: Allocating EventArgs...</p> <p>Isn't this why &nbsp;EventArgs.Empty exists?</p> <p>-Brandon Bloom</p> http://blogs.msdn.com/shawnhar/archive/2007/07/09/delegates-events-and-garbage.aspx#3800073Tue, 10 Jul 2007 18:50:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:3800073ShawnHargreaves<p>EventArgs.Empty is good if you have no arguments to pass, but won't help if you do actually have a custom argument type and want to put some real data in there. I don't have a good feeling for how many events have no args, but it's maybe 50/50?</p> http://blogs.msdn.com/shawnhar/archive/2007/07/09/delegates-events-and-garbage.aspx#3815899Wed, 11 Jul 2007 17:46:40 GMT91d46819-8472-40ad-a661-2c78acb4018c:3815899andyl<p>Thanks for elaborating on the event/delegate issue - passing structs by reference is working fine for me, and will do until XNA supports a generational GC (come on Shawn, you *know* you need one! ;)</p>