Multi-size mosiac bug?

Hi guys,

Not sure if this belongs to a certain toolbox, because I have install all toolboxes and am using SNAP 6, but,

I have been trying to run Geometric Operations > Multi-size Mosiac, but it gives me strange behavior and an error.

Firstly there are two options to select from, neither of them work.

Secondly, they both give me an error. Specifically:

SEVERE [global]
java.lang.NullPointerException: No 'delegate' in BinaryFileMap@5e31702d{fo=MultiFileObject@2e60b372[Actions/Operators/org-esa-s2tbx-dataio-mosaic-ui-multiSizeMosaicAction.instance]}
	at org.openide.awt.AlwaysEnabledAction.getDelegate(
	at org.openide.awt.AlwaysEnabledAction.actionPerformed(
	at javax.swing.AbstractButton.fireActionPerformed(
	at javax.swing.AbstractButton$Handler.actionPerformed(
	at javax.swing.DefaultButtonModel.fireActionPerformed(
	at javax.swing.DefaultButtonModel.setPressed(
	at javax.swing.AbstractButton.doClick(
	at java.awt.MenuItem.processActionEvent(
	at java.awt.MenuItem.processEvent(
	at java.awt.MenuComponent.dispatchEventImpl(
	at java.awt.MenuComponent.dispatchEvent(
	at java.awt.EventQueue.dispatchEventImpl(
	at java.awt.EventQueue.access$500(
	at java.awt.EventQueue$
	at java.awt.EventQueue$
	at Method)
	at java.awt.EventQueue$
	at java.awt.EventQueue$
	at Method)
	at java.awt.EventQueue.dispatchEvent(
	at org.netbeans.core.TimableEventQueue.dispatchEvent(
[catch] at java.awt.EventDispatchThread.pumpOneEventForFilters(
	at java.awt.EventDispatchThread.pumpEventsForFilter(
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(
	at java.awt.EventDispatchThread.pumpEvents(
	at java.awt.EventDispatchThread.pumpEvents(

Is this a bug, or something I need to fix on my end? And if so how?


it is very strange to have two options for Multi-size Mosaic, perhaps something was wrong during your installation. I would suggest to uninstall SNAP and install it again from scratch (and update it from Tools -> Plugins -> Update) to see if the error persists.

Thanks, I uninstalled with the uninstalled tool, and reinstalled normally this seems to have fixed the problem.

It probably occurred because the previous install was an update install from 5.0 to 6.0.