Immediate and reproducible stack overflow on "Synchronize Workspace" [message #1819142] |
Wed, 08 January 2020 17:25 |
Michael Moser Messages: 64 Registered: October 2012 Location: Zürich, Switzerland |
Member |
|
|
Whenever I try to "Synchronize Workspace" I reproducibly get a stack overflow.
An internal error occurred during: "Updating Synchronize view for Git without local changes.".
java.lang.StackOverflowError
This is in Eclipse 2019-12 (but was already the case in earlier builds). It's getting might annoying! Using Java v8 (AdoptOpenJDK / jdk-8.0.222.10-hotspot).
What can I check or do to avoid or fix that?
- Remove something from .metadata?
- Start with a new workspace? :-(
- Other fixes?
Is there something I can contribute to analyze this?
I have a not so big workspace (containing maybe 15 medium sized projects). Nothing spectacular (I have worked with work spaces and projects at least 20 times that size before and had no such issue!). Beats me, what could cause this StackOverflow...
[Updated on: Wed, 08 January 2020 17:27] Report message to a moderator
|
|
|
|
|
|
|
|
Re: Immediate and reproducible stack overflow on "Synchronize Workspace" [message #1820653 is a reply to message #1819371] |
Fri, 24 January 2020 22:15 |
Michael Moser Messages: 64 Registered: October 2012 Location: Zürich, Switzerland |
Member |
|
|
What kind of resources could that possibly be? If I right-click on any of the projects' root -> Properties -> Resources -> Linked Resources the list is empty. But I guess that's not what you meant by "some type of linked resource that links up to its own parent", is it? Could you elaborate a bit more what you meant by that?
As I wrote: this happens even in a newly created workspace just by importing a nested Maven project (nested meaning a parent project containing about a dozen of sub-projects).
Anyone familiar with Eclipse's internals to explain or guess what could possibly cause such loops? After all: the project builds, runs test and installs all fine when I issue e.g. a "mvn install" on the command line, so it can't be that off and totally corrupted...
[Updated on: Fri, 24 January 2020 22:22] Report message to a moderator
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02609 seconds