Bug 567289 - heapstatus not customizable with using preferenceCustomization or -pluginCustomization
Summary: heapstatus not customizable with using preferenceCustomization or -pluginCust...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.15   Edit
Hardware: PC Windows 10
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-23 09:39 EDT by Reto Urfer CLA
Modified: 2020-09-25 09:36 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Reto Urfer CLA 2020-09-23 09:39:43 EDT 
The preferences for the plugin org.eclipse.ui are prooerly initialized using the value from the property file specified by preferenceCustomization or -pluginCustomization.

Unfortunately the method initializeDefaultPreferences() of the class org.eclipse.ui.internal.WorkbenchPreferenceInitializer located in plugin org.eclipse.ui.workbench is always executed after the preference initialization of the plugin org.eclipse.ui and overwrites always the configured with its default property values (see the following code snippet).

// Heap status preferences is stored in different node		IEclipsePreferences heapNode = context.getNode("org.eclipse.ui"); //$NON-NLS-1$
heapNode.putBoolean(IWorkbenchPreferenceConstants.SHOW_MEMORY_MONITOR, false);
node.putInt(IHeapStatusConstants.PREF_UPDATE_INTERVAL, 500);
node.putBoolean(IHeapStatusConstants.PREF_SHOW_MAX, false);
node.putBoolean(IPreferenceConstants.OVERRIDE_PRESENTATION, false);
 
As a workaround I tried to explicitly start the plugin org.eclipse.ui.workbench with a lower start level but with no success. The problem most probably was alreay existing in earlier releases but with Eclipse 4.15 the default value of the property org.eclipse.ui/SHOW_MEMORY_MONITOR has been changed from true to false and now it is not possible anymore to make the heapstatus visible in a RCP application.