Table of Contents

Eclipse IDE

Each IDE distributed by the Eclipse Foundation is composed from the contents of a number of Eclipse projects. Generally each project contributes its content to the Eclipse Simultaenous Release. The Eclipse Packaging project assembles a subset of the project content into the various IDEs making them available on the download page and in the Eclipse Installer This diversity of contribution makes it challenging to report an issue to the project that contributes the faulty component. Moreover, it's not possible to transfer issues across GitHub organizations so ideally one reports an issue with the right project's organization.

Problem Reporting

This page adapts itself to the product from which it is opened via the Help → Report a Problem menu. The sidebar to the right lists the projects that are incorporated into the IDE package you are using. Of course you may well have installed additional features from the Eclipse Simultaenous repository, or even from Eclipse Marketplace. In any case, the list on the side bar to the right is a good place to start. Please have a quick read though the description for the project to determine if that is indeed a suitable place to report an issue. Please also resource the following advice at least once to ensure that you submit a high-quality problem report.

Details, Details, Details...

When reporting issues, providing appropriate details is the key to success. The developer will need to know which version of which software you using.

Most important, the developer will need to know how to reproduce the problem that you are seeing. If the developer can't reproduce the problem, it won't be fixed. Better to provide too much detail than not enough. A picture is worth a thousand words. All browsers provide really good support for simply copying a screen capture and pasting it into the issue entry field. It's also easy to drag and drop a short video or a zip file containing a sample for reprodcing the problem.

The Error Log

Often when things good badly wrong, errors are logged. You can open the Error Logview via quick search.

The view contains useful details for helping track down a problem.

You can double click an entry to see the details.

Whenever available, please include these detail. Simply use the Copy Event Details to the Clipboard button and paste it into the issue surrounced by ``` in the markdown to format it nicely.

```
eclipse.buildId=4.35.0.20250306-0811
java.version=21.0.2
java.vendor=Eclipse Adoptium
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.committers.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.committers.product

org.eclipse.ui.ide
Error
Fri Apr 04 15:21:14 CEST 2025
Not properly disposed SWT resource

java.lang.Error: SWT Resource was not properly disposed
	at org.eclipse.swt.graphics.Resource.initNonDisposeTracking(Resource.java:184)
	at org.eclipse.swt.graphics.Resource.(Resource.java:121)
	at org.eclipse.swt.graphics.Image.(Image.java:552)
	at org.eclipse.jface.resource.URLImageDescriptor.createImage(URLImageDescriptor.java:306)
...
```

Open Discovered Type

The Java source code of all Eclipse Foundation projects is indexed. You can use Navigate → Open Discovered Type to search this index. If you copy a class name, e.g., org.eclipse.swt.graphics.Resource, from the stack trace in the error log, you can locate the source code.

Note in particular that this gives you information about the GitHub or GitLab oganization and even the repository of that organization, e.g., https://github.com/eclipse-platform/eclipse.platform.swt. Keep in mind that problems are often caused by misuse of the framework farther down in the stack. Also, stack traces are often long chains of exceptions where typically the final exception (cause) is the most signfiicant. In this specific case, SWT provides support for tracking cases where other software is not properly disposing resources, leaking handles which will eventually force the application to require a restart.

Introspection with Plug-in Spies

The IDE includes so-called spies that can be used to introspect what you see in the IDE. This is useful for determine project contribute any particular aspect of the IDE. Here we use quick search to see the convenient keyboard shortcuts for these actions:

Plug-in Selection Spy

Here we have used Help → Eclipse Marketplace to bring up Marketplace dialog and used the Plug-in Selection Spy key combination to bring up the spy dialog:

So we know this dialog is provided by org.eclipse.epp.mpc.ui. In addition, we also see the class names which we can use with Navigate → Open Dicovered Type. As such if we have issues with this dialog, we know to open the issue with the Marketplace Client project.

Here we have used the Plug-in Menu Spy key combination active the menu spy before brining up the context menu:

This of course also works for the menu bar. Note that the cursor changes to indicate the menu spy is active. Clicking on a menu item will open the Plug-in Menu Spy dialog.

So we know this is provided by org.eclipse.lsp4e.menu.refactorings and can find the LSP4E project.

Simultaneous Release Projects

The following is a list of all projects that contribute to the Simultaneous Release. These are the projects most likely to be installed in your IDE. Each project is decorated with the branding icon of each IDE in which it is installed by default, and each provides is a short description as well a link to the project's website. Most important, there is a link to the project's GitHub or GitLab organization for reporting issues against one of that project organization's repositorie which are also listed.