GoogleCodeExporter
commented
8 years ago Added state to PooledObject to determine if an object is alive or dead.
Objects were being updated when they were no longer in the render context. It
seems that FF4.0b1 is more sensitive to objects being removed from the scene
graph than 3.6 or prior versions of Firefox were.
In the Asteroids example, the bullet object was being destroyed while it was in
the process of being updated. This would cause an object to fail during update
since it had been destroyed and subsequently removed from the scene graph.
After fixing this issue, it became apparent that this problem has existed for a
while and that checking for an object to be alive before performing any updates
on it would be a good sanity check.
However, the sanity check failed because (for example) when a bullet struck an
asteroid, the asteroid was destroyed as well. The asteroid would be removed
from the render context, but the render context was already iterating over its
objects. Thus, when it came to the rock which was destroyed (which existed
after the bullet in the scene graph) it would fail the "isAlive()" check.
Hence, objects are now added to a safeDelete() list when they are destroyed.
This is automatic to make sure that objects whose destroy() methods are called
are put into the list and destroyed after the default rendering context has
finished updating.
The issue has been fixed and testing in FF4.0b1, FF3.6.6, and Chrome 5.0Original comment by bfatt...@gmail.com on 13 Jul 2010 at 2:28
- Changed state: Fixed
Original issue reported on code.google.com by
bfatt...@gmail.comon 12 Jul 2010 at 4:11