Eclipse took overnight to close and is still trying to close - eclipse

I tried closing Eclipse because there was a bug in the Java code, and then I successfully closed it. "Success" may not be what was expected. Now, the closing message shows up... I thought it would finally close after I went to sleep, but NO! It's still on and I don't know what happend to Eclipse. Here's the message:
Does anyone know what's wrong with Eclipse? I have no clue why this is happening, and I can't even open eclipse anymore, but that's a different problem.
Thanks for anyone who could help.

Related

Why is terminal crashing when I should be getting an error message?

My apologies if this is an overly nooby question. I'm just learning Ruby and my terminal has started acting funny and I'm not sure how to fix it. I appreciate any guidance that can steer me in the right direction.
First, when I open terminal within VS Code I have started to get the following message - "complete:13: command not found: compdef". As a newcomer, I am not very skilled yet with zsh and not sure what to do to fix this message.
Second, ever since this message started appearing, whenever I run ruby code and expect an error, instead of getting an error message, the terminal just seems to crash. The cursor moves to the next line and then nothing happens other than the fan speeding up. I can type text but the only way to get the terminal working again is to close out and reopen. Is this related to the compdef message I am getting or is this a separate message? Does anyone know how I might go about fixing this? It's preventing me from being able to learn where I am going wrong in my code.
Thank you so much to anyone that may have an answer!

Eclipse error log pops up after every save

Whenever I make any edits in eclipse (using STS) and save them the error log pops up. It's extremely annoying and I have no idea how to get rid of it. Anyone face a similar issue and how to resolve it?

Eclipse Code Corrupted after Crash

I closed Eclipse because I had a feeling my PC was gonna crash (been acting funny today), and it said it saved my workspace and closed normally.
But when I went back in after reboot, my workspace wasn't loading - even after selecting the right one my projects wouldn't show and the layout was reverted to default....not such a big deal, just re-imported.
But... One of the source files I was working on seems to have been corrupted, replaced with one continuous line of squares, which is kind of a big deal :/
Any thoughts on what caused this? I know there's probably no chance of getting that file back, but if anyone has had a similar experience or knows what the jaysus happened that'd be cool! Ideally I'd like if this never happened again...
Problem was related to my SSD: Weird bug where after 5184 hours of use it would shutdown.
Firmware update fixes the problem.
More here: http://www.tomshardware.com/news/Crucial-m4-Firmware-BSOD,14544.html

Eclipse Scala plug-in: "illegal cyclic inheritance"

I just updated to the latest Scala-IDE version on Eclipse, and it's highlighting loads of spurious "illegal cyclic inheritance" errors in code I know to be OK (it was before, and it still compiles and runs OK).
Any way to fix this? If not, how do I roll back to the previous version? I don't see any options to roll back or download earlier versions on the Scala IDE website.
Thanks.
edit: Never mind, it spontaneously sorted itself out after about 10 minutes sitting there showing errors. Will leave question here in case else anyone gets this.
"Project -> Clean Project" always helps me when Scala-IDE is showing weird error messages.
Sometimes errors will show in the editor, but not in the package explorer. Things still appear to compile ok when that occurs.

Netbeans 6.7 freezes on launch after crash. Any hints?

My wonderful corporate Dell crashed when "hibernating", and now NetBeans freezes when launching. (It displays the full interface, and starts "Scanning Projects", but doesn't get past there and I can't click on anything.)
I imagine there's some cache somewhere to clear out or something. Anyone know where?
I kinda had that type of problem before. What I end up doing to resolve that problem is to remove all the project entries that were loaded but not closed when I closed the problem. They are in:
.netbeans/6.X/config/Preferences/org/netbeans/modules/projectui.properties
In the entries:
openProjectsDisplayNames.0=PROJECTNAME
openProjectsURLs.0=file:/PATH/TO/PROJECT