Community
Participate
Working Groups
WorkbenchImages.declareImage does not check for null before accessing the imageRegistry member. This member is lazily initialized in the implementation of WorkbenchImages.getImageRegistry. Before the patch for bug#32147, this happened to work because getImageRegistry was called from Workbench. initializeImages. When I removed that call, I observed the NPE. As a work-around for now I've left in the call to #getImageRegistry, even though nothing is done with the result. When this bug is fixed, we should also remove the call from Workbench.initializeImages.
I think this is now obsolete.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.