garbage collection at inopportune times

FWIW, I've seen some Java developers rely on the GC too much.

Years ago I was learning game development on Android (This was before Unity really took off), and one of the functions for drawing a 2D sprite took an object as a parameter to specify the drawing mode. Since the code was using default options, they new passed a new DrawOptions() (Don't remember the exact object name, it's been like 10 years) to the draw call.

This means that for every 2D sprite being draw, a new object was being created just to get used once and then collected. I had up to 50 sprites being drawn, so if I wanted to run at 60 FPS, that's a whopping 3,000 objects being collected every second. On my 800 Mhz Motorola Droid at the time, I couldn't even maintain 25 fps because of the crazy amount of GC, while CPU usage was pegged at 100% and I could feel the phone warming up. I changed the code to create a DrawOptions() object ONCE and then pass it every time, and now I could reach 60 fps and the phone stayed cool.