nsImageManager uses static constructors to initialize gImageManager. Static constructors are banned by the portability standards (see http://www.mozilla.org/docs/tplist/catBuild/portable-cpp.html#dont_use_static_constructors) because they make it very difficult to port the code to other platforms (many platforms don't call static constructors on loading shared libraries). On a lot of platforms, the viewer crashes at startup because gImageManager is 0.

kipp, is this still an issue given your latest changes?

Setting all current Open/Normal to M4.

per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser

the image manager should become a service and this problem will go away.

Wellll, it looks like the gfx Image Mananger isn't going away anytime soon. -pn

ImageManager has been made a service. see bug #15820

Akkana, Would you like to confirm that this is addressed to your satisfaction, and mark it as Verified/Fixed? (Otherwise, I'll just rubber-stamp it as Verified.) Thanks!

gImageManager is no longer statically initialized. However, it is now a pointer, and it isn't initialized to zero. Some platforms don't automatically initialize variables to zero, so this won't always work on all platforms. This really should be initialized to zero for portability.

Clearing FIXED resolution due to reopen.

Checked in a fix. Initialized gImageManager to zero.

Akkana, would you like to re-verify this? Otherwise, I can rubber-stamp it verified without inspection. Thanks!

Sorry, I thought I marked this verified a while ago. It looks fine now -- trying again. :-)

Thanks, Akkana!