Bug 468329 - Java Error and windows 8
Summary: Java Error and windows 8
Status: CLOSED DUPLICATE of bug 221969
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.5   Edit
Hardware: PC Windows 8
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-26 10:27 EDT by Craig Adams CLA
Modified: 2015-05-26 10:55 EDT (History)
2 users (show)

See Also:


Attachments
A screen shot of the error. (128.36 KB, image/jpeg)
2015-05-26 10:27 EDT, Craig Adams CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Craig Adams CLA 2015-05-26 10:27:25 EDT
Created attachment 253783 [details]
A screen shot of the error.

Hi 

I am having a problem of getting eclipse to run on one of the computer as come up say there a error with Java saying exit code=13. This only happen on windows 8.1 but work on a different computer with windows 7.
Comment 1 Lars Vogel CLA 2015-05-26 10:33:55 EDT
Please share the output of: 

java -version
Comment 2 Craig Adams CLA 2015-05-26 10:39:17 EDT
(In reply to Lars Vogel from comment #1)
> Please share the output of: 
> 
> java -version


This output.

C:\Users\**************>java -version
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b15)
Java HotSpot(TM) Client VM (build 25.45-b02, mixed mode, sharing
Comment 3 Andrey Loskutov CLA 2015-05-26 10:44:54 EDT
Please run "java -verbose" and check if the java path reported by java matches the one visible in your screenshot.
Comment 4 Lars Vogel CLA 2015-05-26 10:54:13 EDT
(In reply to Craig Adams from comment #2)
> C:\Users\**************>java -version
> java version "1.8.0_45"
> Java(TM) SE Runtime Environment (build 1.8.0_45-b15)
> Java HotSpot(TM) Client VM (build 25.45-b02, mixed mode, sharing

Thanks, see http://www.vogella.com/tutorials/Eclipse/article.html#solvingthe3264issue for this issue.
Comment 5 Lars Vogel CLA 2015-05-26 10:55:55 EDT

*** This bug has been marked as a duplicate of bug 221969 ***