1. I miss strict or superstrict. Without them, several scope optimations don't exist. Might cause some of the problems if not all of them.
2. You are right, you don't need to null.
But as you defined your array global it might be wise to do it. A global never goes out of scope and is handled differently than locals when it comes to automatic cleanup.
3. If both does not change anything, create a bug thread.
In that case I assume that the issue behind this one is similar to the issue behind "why images don't survive fullscreen -windowed" changes anymore
2. You are right, you don't need to null.
But as you defined your array global it might be wise to do it. A global never goes out of scope and is handled differently than locals when it comes to automatic cleanup.
3. If both does not change anything, create a bug thread.
In that case I assume that the issue behind this one is similar to the issue behind "why images don't survive fullscreen -windowed" changes anymore