Eclipse crashes on start but no log [message #1767687] |
Sun, 09 July 2017 18:58  |
Eclipse User |
|
|
|
I'm not an Eclipse newcomer but it's so rare that I use these forums that I've forgotten where I should ask this type of question and the FAQ I read said this sort of problem should be asked in the Newcomers area so here I am.
I have three versions of Eclipse installed on this laptop but, in truth, I've only ever used the Mars version; I *started* the Oxygen version and closed it after the briefest of looks. The Mars version is 3.5.2 if I recall correctly - it says Mars.2 on the splash screen when it launches properly - and I have Windows 10 on this machine.
Mars was working just fine as recently as this morning but I had to do a reboot of Windows due to an unrelated issue and now when I try to launch Mars, I get a fleeting glimpse of the splash screen, then it apparently crashes. I do NOT get any kind of exit code and I can't find any log from today where the FAQ says to look for it. There *are* logs in eclipse\configuration but the newest is dated 6 days ago. I know I should look in the workspace too but I can't *find* the workspace and don't remember where it should be. (A while back, I checked the option that said "Always use this workspace" and now I've forgotten where it was.) I've used the File Explorer search option to look for it but have come up empty. Yet it was there a few hours ago and I can't think of anything I've done that could delete it. Even if it is really deleted, shouldn't Eclipse tell me that, instead of just crashing silently? For what it's worth, I've looked in the Recycle Bin and can't find workspace there either. However, I don't really believe it is gone: I *thought* it was right in the C: directory but noticed it wasn't there at least a week ago, yet it still found my code just fine and let me edit it and run it.
I've tried using --consoleLog (Runtime) in the eclipse.ini file but that doesn't change anything either.
My eclipse.ini points to a valid, recent VM (jdk1.8.0_131) and the VM is still exactly where it is indicated by the ini file, I even made sure that javaw.exe is in the bin directory.
I've also done multiple Windows reboots on the off-chance it might be some sort of Windows-related foolishness but that didn't help either except to the VERY limited extent that the *first* time I tried to launch Mars, the splash screen stayed visible for maybe 10 or 15 seconds before crashing; on every subsequent attempt it would give the briefest flicker, then crash.
I need some help to figure this out. I *really* need to get this working again. Can anyone help me troubleshoot this?
[Updated on: Sun, 09 July 2017 19:08] by Moderator
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: Eclipse crashes on start but no log [message #1768220 is a reply to message #1767983] |
Fri, 14 July 2017 14:49   |
Eclipse User |
|
|
|
I have some additional information on my situation, as well as some questions.
First, I downloaded a bunch of JavaFX samples some time last week consisting partly of some standalone jars. Last week, they ran perfectly fine simply by double-clicking on them. Now, they don't run at all. When I clicked on "Open With...", the default option for jar files was Java Platform SE Binary; I'm not sure if that's what *should* be there.
Second, I've already mentioned that my problem only began several days after I had made some changes to my environment variables. I assumed that those changes couldn't have anything to do with the problem because I'd used Eclipse without difficulty for several days after those changes. It suddenly dawned on me that I'd omitted mentioning one key thing: I don't reboot Windows very often, rarely more than a couple of times a month. I'm pretty sure that I did not reboot Windows in between the time I made the environment variable changes and the emergence of my problem with Eclipse. Given that my problem began when I did finally do a reboot, it seems likely that I messed something up with either the changing of the environment variables or the installation of the newest JDK and JRE or the removal of the old JDKs and JREs.
Is there any kind of checklist I can follow that will tell me EVERYTHING that has to be in place and correct before Eclipse will run on a Windows 10 machine? I've almost certainly messed *something* up but I don't know what is wrong. I'm guessing that Eclipse only fails silently like this under a very limited set of circumstances and that someone can point me to documentation on what those circumstances are. If I can go through a checklist, I should be able to identify what is broken and fix it.
Or is there some other place I should be looking for messages/logs that I haven't tried yet? I've pretty much only looked in \eclipse\configuration for .log files and have yet to see one dated after July 3. When I've tried launching eclipse from the command line, I've also looked for messages but haven't seen any. Maybe there is some other place to look for messages that might help me figure this out?
One other thing. Someone helping me on another forum said he used to find it necessary to make sure that there is a copy of java.exe, javaw.exe, and javaws.exe to be in the \Windows\System32 folder for things to work properly. I did not have any of those files in my \System32 folder so I copied them in there but it didn't change any of the symptoms I'm getting. However, when I looked at my classpath, I noticed that the first path in it was the c:\ProgramData\Oracle\Java\javapath and *that* folder DID have copies of java.exe, javaw.exe, and javaws.exe. Is that how things *should* be in a Windows 10 64-bit machine? Is there any harm in deleting the copies that I put in the \System32 folder?
|
|
|
Re: Eclipse crashes on start but no log [message #1768403 is a reply to message #1768220] |
Tue, 18 July 2017 06:39  |
Eclipse User |
|
|
|
For the sake of posterity, I just want to report that I've finally gotten past my problem with Eclipse.
I uninstalled both the JDK and JRE and reinstalled them. Eclipse immediately started working again. I did *not* have to mess with the environment variables at all to get Eclipse working. I'm not quite sure what was messed up but the uninstall/reinstall of the JDK and JRE solved the problem.
It would be FANTASTIC if the developers made an effort to anticipate whatever happened to me so that some kind of diagnostic/error message can be generated when the next poor sod does whatever I did to myself. I've lost so much precious time - and momentum! - these last several days. I just hope I can recapture it and make up for lost time.....
|
|
|
Powered by
FUDForum. Page generated in 0.09575 seconds