Log the number of objects in a Pack when it is deleted in debug builds to hel...

Log the number of objects in a Pack when it is deleted in debug builds to help JS app developers find leaks.

TEST=used it in a JS app to help identify a leak
BUG=none

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=75441

[zhurunz, 2011-02-18 20:45:01]

Should this be an assert also?

[milligan, 2011-02-18 20:45:58]

LGTM

[Tristan Schmelcher 2, 2011-02-18 20:55:10]

On 2011/02/18 20:45:01, zhurunz wrote:
> Should this be an assert also?

Tim suggested the same thing. I'm not making it an assert because currently
there always at least a couple dozen objects still around, so it would assert
all the time.

Also, it isn't actually bug in O3D for there to be objects left, because the
owned_objects_ destructor unrefs them and they are then deleted just fine. But a
large number of objects would be indicative of a bug in the JS app, because it
probably should have called Pack.removeObject earlier to delete them when they
were no longer needed rather than leaving them all around until shutdown.

[gangji, 2011-02-18 21:13:41]

LGTM