Bug 27075 ViewerSorter could maybe lazily initialize Collator
calling JavaElementSorter creates a lot of new objects (ViewerSorter calls Collator.getInstance() which is the culprit) so maybe fSorter could be initialized lazily
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/MembersOrderPreferencePage.java
private static final String ALL_ENTRIES= "T,SI,SF,SM,I,F,C,M"; 
	private static final String PREF_OUTLINE_SORT_OPTION= PreferenceConstants.APPEARANCE_MEMBER_SORT_ORDER;
	private static String CONSTRUCTORS= "C"; 
	private static String FIELDS= "F"; 
	private static String METHODS= "M"; 
	private static String STATIC_METHODS= "SM"; 
	private static String STATIC_FIELDS= "SF"; 
	private static String INIT= "I"; 
	private static String STATIC_INIT= "SI"; 
	private static String TYPES= "T"; 
	public static final int TYPE_INDEX= 0;
	public static final int CONSTRUCTORS_INDEX= 1;
	public static final int METHOD_INDEX= 2;
	public static final int FIELDS_INDEX= 3;
	public static final int INIT_INDEX= 4;
	public static final int STATIC_FIELDS_INDEX= 5;
	public static final int STATIC_INIT_INDEX= 6;
	public static final int STATIC_METHODS_INDEX= 7;
	
	private static final int LAST_INDEX= STATIC_METHODS_INDEX;
	private final int DEFAULT= 0;
	private ListDialogField fSortOrderList;
	private static Cache fgCache= null;
	private static class Cache implements IPropertyChangeListener {