Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NPE in ConfigurableMergeAction#selectionChanged #77

Closed
jhonnen opened this issue Sep 27, 2018 · 6 comments
Closed

NPE in ConfigurableMergeAction#selectionChanged #77

jhonnen opened this issue Sep 27, 2018 · 6 comments

Comments

@jhonnen
Copy link
Contributor

jhonnen commented Sep 27, 2018

With subclipse 4.2.7 and eclipse 4.9 the following NPE occurs sporadically on text selections:

java.lang.NullPointerException
	at org.tigris.subversion.subclipse.ui.internal.TeamAction.selectionChanged(TeamAction.java:256)
	at org.tigris.subversion.subclipse.ui.actions.ConfigurableMergeAction.selectionChanged(ConfigurableMergeAction.java:23)
	at org.eclipse.ui.internal.PluginAction.refreshEnablement(PluginAction.java:209)
	at org.eclipse.ui.internal.PluginAction.selectionChanged(PluginAction.java:276)
	at org.eclipse.ui.internal.PluginAction.selectionChanged(PluginAction.java:300)
	at org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(SelectionService.java:242)

The exception is thrown because getTargetPart().getSite().getPage() returns null. The action's target part is a disposed editor. The PartSite of disposed parts no longer has a reference to its original workbench page (since eclipse 4.9, see Bug 536677).

ConfigurableMergeAction#setActivePart(IAction, IWorkbenchPart) is apparently never called.

Full stacktrace: stacktrace.log

@Marco-Sulla
Copy link

I have the same problems. This is fixed in what version of Subclipse?

@Marco-Sulla
Copy link

Please, can you answer me? This bug bothers me a lot. I have Subclipse 4.3.0.201901172050 with Eclipse 20190314-1200, on Lubuntu 18.04.2 64 bit. I'm using Java Azul Zulu 8.

@Marco-Sulla
Copy link

Hello?

@markphip
Copy link
Contributor

markphip commented Jun 4, 2019

The fix committed in this issue would be included in the 4.3.0 release. Open a new issue with the new stack trace and if possible add a PR with the fix.

@Marco-Sulla
Copy link

Marco-Sulla commented Jun 4, 2019

4.3.0 release is out. So the fix is included?

And PR stands for...?

@markphip
Copy link
Contributor

markphip commented Jun 4, 2019

PR stands for Pull Request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants