| Issues updating Eclipse | 2018-12 → 2019-03 [message #1804612] |
Fri, 29 March 2019 13:28  |
 Alessandro Aiezza
Messages: 38
Registered: February 2017
Location: Nashville, TN |
Member |
|
|
This morning I updated to 2019-03 from 2018-12 and it broke my workspace so badly!
I've attached my log dump.
When I went to update this morning, I was under the assumption it was just my plugins, as usual, that needed updating. However, my entire eclipse installation got an upgrade as well. Exciting at first! And then realized I hadn't backed up my workspace in a while (Something CRUCIAL to my day job)
I had auto-building on and when eclipse got around to building my open project, it crashed.
I restarted eclipse, and had just enough time to turn that feature off. That bought me about 5 more minutes, during which time I was able to push a commit to a git repository that had already been committed from yesterday.
Shortly after getting that branch pushed though, Eclipse crashed again.
Now I cannot keep it open for more than 5ish minutes until, I can only imagine, some plugin tried to do something that ends up not working.
It is frustrating that everytime I upgrade my Eclipse IDE, the proper checks aren't performed for me to at least discover what else I need to have downloaded in my workspace in order for it to work. It's just way too complicated to figure out and to navigate. Please help me fix this!
The update process is seriously so debilitating for Eclipse. Speaking as a user for the last 7 years now, I can only say how disappointed I am... I have work to do, please fix this.
Attachment: 201903.log
(Size: 18.90KB, Downloaded 150 times)
|
|
|
|
|
|
| Re: Issues updating Eclipse | 2018-12 → 2019-03 [message #1804627 is a reply to message #1804624] |
Fri, 29 March 2019 17:04  |
Alessandro Aiezza
Messages: 38
Registered: February 2017
Location: Nashville, TN |
Member |
|
|
Since this morning, I've decided to start anew with a fresh workspace. I was able to move some preferences and my perspectives over, so it wasn't all bad.
Unfortunately a couple things have occurred: 1) I tried importing my MyLyn tasks in an exported zip into the new workspace and this migration caused eclipse to crash. 2) While doing something in the command line waiting for eclipse to restart, I accidentally typed `..` and enter into the workspace name prompt. This essentially tried taking `/Applications/Eclipse.app/Contents` and making it into my workspace! Yea... great! As eclipse was starting, it crashed again.
I then deleted that .metadata directory and tried opening eclipse. It consistently crashes now with no hope of opening any workspace.
So I threw my hands up in the air and said I'll just install a new eclipse. Downloaded the installer, installed the regular java IDE one, launched it, had it create a brand new workspace, AND... crash. Only seconds after opening the new workspace. Tried running eclipse again several times. Same and different workspaces. They all crash eclipse.
This is a fresh installation and it's bombing.
[Updated on: Fri, 29 March 2019 17:19] Report message to a moderator |
|
|
| Re: Issues updating Eclipse | 2018-12 → 2019-03 [message #1804631 is a reply to message #1804627] |
Fri, 29 March 2019 17:14 |
|
no
My best guess is that you updated Xtext as part of your overall update and that this version of Xtext relies on a newer version of org.objectweb.asm but they forgot to change the lower bound on their dependency to ensure that this newer version is installed/updated, not just some older version that would be lacking the some APIs that it uses.
is 7 to 8 exclusive.
but that is xtext 2.17 not xtext 2.12.
=> where does your xtext 2.12 come from.
Twitter : @chrdietrich
Blog : https://www.dietrich-it.de
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Issues updating Eclipse | 2018-12 → 2019-03 [message #1804665 is a reply to message #1804661] |
Fri, 29 March 2019 18:47 |
|
xtext Xtext - 2.12 needs asm 5.0.1 that is not there.
i dont know xtext wont get updated in your setup and how your available update sites look like
i dont know if where is anything in spring that needs that.
i assume that additionally installing asm 5.0.1 from the orbit update site could resolve that issue. (it should be in the list if you add the update site and untick categorize plugins and show latest only)
(i recommend you to do a backup before trying)
Twitter : @chrdietrich
Blog : https://www.dietrich-it.de
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Issues updating Eclipse | 2018-12 → 2019-03 [message #1804810 is a reply to message #1804705] |
Mon, 01 April 2019 15:13 |
Alessandro Aiezza
Messages: 38
Registered: February 2017
Location: Nashville, TN |
Member |
|
|
Ok So I've began the process of setting up my workspace again from scratch with the exception of me importing my preferences because I really like my perspectives (which I realize are reproducible with simple screenshots). However, at random points in the use of eclipse, it will crash without warning and nothing pertaining to the crash will be logged.
Here is all I see in the logs before the crash directly after selecting a new workspace.
!SESSION 2019-04-01 10:29:12.305 -----------------------------------------------
eclipse.buildId=4.11.0.I20190307-0500
java.version=1.8.0_192
java.vendor=Oracle Corporation
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product -keyring /Users/alex.aiezza/.eclipse_keyring
Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.jee.product -keyring /Users/alex.aiezza/.eclipse_keyring
!ENTRY org.eclipse.egit.core 1 0 2019-04-01 10:29:22.914
!MESSAGE Using Apache MINA sshd as ssh client.
!ENTRY org.eclipse.jface 2 0 2019-04-01 10:29:23.817
!MESSAGE Keybinding conflicts occurred. They may interfere with normal accelerator operation.
!SUBENTRY 1 org.eclipse.jface 2 0 2019-04-01 10:29:23.817
!MESSAGE A conflict occurred for COMMAND+SHIFT+T:
Binding(COMMAND+SHIFT+T,
ParameterizedCommand(Command(org.eclipse.jdt.ui.navigate.open.type,Open Type,
Open a type in a Java editor,
Category(org.eclipse.ui.category.navigate,Navigate,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@4dc16fc9,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)
Binding(COMMAND+SHIFT+T,
ParameterizedCommand(Command(org.eclipse.lsp4e.symbolinworkspace,Go to Symbol in Workspace,
,
Category(org.eclipse.lsp4e.category,Language Servers,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@1028a747,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)
!ENTRY org.eclipse.jface.text 2 0 2019-04-01 10:29:26.275
!MESSAGE Duplicate template id: 'org.eclipse.wst.xslt.templates.xpath.boolean'
It seems that since starting a new workspace too that the guice and asm stuff has stopped becoming an issue. I am at a loss for how to proceed.
In fact, since the last crash, I haven't been able to open the same workspace again at all.
$ eclipse/jee-2019-03/Eclipse.app/Contents/MacOS/eclipse
org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
org.eclipse.m2e.logback.configuration: Logback config file: /Users/alex.aiezza/workspace/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.1.11.0.20190220-2119.xml
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [bundleresource://940.fwk626889335:1/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://940.fwk626889335:2/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
org.eclipse.m2e.logback.configuration: Initializing logback
Killed: 9
I don't know how silly this is to ask, but should I attach my workspace here so it can be used for debugging?
It feels like to much to ask from a non-paid support team/community. I guess this could be happening to someone else so it [b]may[\b] be worth it. But I also don't know how much PII will be persisted in a typical eclipse workspace metadata directory.
Thoughts?
[Updated on: Mon, 01 April 2019 15:38] Report message to a moderator |
|
|
|
|
| Re: Issues updating Eclipse | 2018-12 → 2019-03 [message #1804821 is a reply to message #1804819] |
Mon, 01 April 2019 18:43 |
Alessandro Aiezza
Messages: 38
Registered: February 2017
Location: Nashville, TN |
Member |
|
|
Ed Merks wrote on Mon, 01 April 2019 13:29You seem to be using a great many technologies any of which might be buggy, and none of this relates at all to JDT so it's unlikely someone will be able to help you with such problems on this forum.
And what exactly do you mean by a "crash"? The JVM just up and died and did a JVM core dump? That's very rare... Or Eclipse just stopped working without logging anything?
Eclipse starts, I choose a workspace, I watch the splash screen claiming to be loading my workspace, and then the app is killed with 9 code.
It appears that java continues to hang in the background actually after this happens. But I get no logging anywhere that I know of. Particularly in the workspace/.metadata/.log file.
[Updated on: Tue, 02 April 2019 21:03] Report message to a moderator |
|
|
|
|
|
|
| Re: Issues updating Eclipse | 2018-12 → 2019-03 [message #1805000 is a reply to message #1804895] |
Thu, 04 April 2019 12:45 |
Alessandro Aiezza
Messages: 38
Registered: February 2017
Location: Nashville, TN |
Member |
|
|
Christian Dietrich wrote on Tue, 02 April 2019 15:37i also wonder if you should use java 8 or 11 instead of the EOL java 9
I don't recall ever saying I was using java 9. This is all with Java 8.
For anyone that happens upon this post: The result for me was to just reinstall version 2018-12 and use a workspace that I (thankfully) had backed up a few months ago. It was lacking some of my settings, but it's the price I paid for blindly updating things in Eclipse and not backing up my workspace in the first place.
I won't be updating again any time soon. And if/when I do, I will backup everything very carefully and probably just try to create a new workspace for that version and then gradually move things over.
The fact that I can "favorite" plugins will hopefully help this process a bit.
[Updated on: Thu, 04 April 2019 12:48] Report message to a moderator |
|
|
|
|
|
|
] 
Search
Help
Register
Login
Home
