Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 369534

Summary:	[Marker Help] Iinvalid registry object when querying marker help
Product:	[Eclipse Project] Platform	Reporter:	Johan Wannheden <johan.wannheden>
Component:	UI	Assignee:	Platform-UI-Inbox <Platform-UI-Inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	stephane
Version:	4.2
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Johan Wannheden

2012-01-24 10:38:18 EST

Build Identifier: M20110909-1335

I'm getting InvalidRegistryObjectException and can backtrack the problem to the following method in the marker help registry where I suspect a missing check on IConfigurationElement#isValid():

org.eclipse.ui.internal.ide.registry.MarkerHelpRegistry.getHelp(IMarker)

IConfigurationElement#getAttribute(String) is used with a configuration element which has become invalid. In the environment which is causing this problem dynamic enabled plug-ins are deployed (installed and uninstalled) at run-time.

Can anyone with more knowledge in this area confirm this bug?

Reproducible: Always

Steps to Reproduce:
1. Start Eclipse run-time
2. Deploy bundle providing marker help extension and a validator creating markers
3. Created markers are correct (marker help works)
4. Uninstall the bundle
5. Re-install the bundle
6. Exception when the Problems view is refreshed (the view previously contained the markers with marker help)

Comment 1 Johan Wannheden

2012-01-25 03:05:20 EST

The problem seems to be that the markerHelp extension point is not dynamic aware. Configuration elements in MarkerHelpRegistry are cached and the cache is not properly updated/reset when extension registry changes occur (see also org.eclipse.ui.internal.ide.registry.MarkerHelpRegistry.helpQueries).

Comment 2 Lars Vogel

2019-11-14 03:10:06 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.