Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 349913 - Crashes at startup after choosing workspace
Summary: Crashes at startup after choosing workspace
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.1   Edit
Hardware: PC Windows XP
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-21 04:52 EDT by Mössenböck Vincenz CLA
Modified: 2011-06-21 10:32 EDT (History)
2 users (show)

See Also:


Attachments
log (225.99 KB, application/octet-stream)
2011-06-21 04:54 EDT, Mössenböck Vincenz CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mössenböck Vincenz CLA 2011-06-21 04:52:21 EDT
Build Identifier: 3.6.2

When I start Eclipse I choose the Workspace, then it loads, shows for half a second the IDE and then it crashes.
I use the IDE in a VM in which I´m working. The place where programms are installed is changed in the registry. I don t want, can t change the place back to original place. 

Reproducible: Always

Steps to Reproduce:
1. Double clicking the Eclipse.exe
2. Confirming the Workspace
3. Then it shows for half a second the IDE and crashes
Comment 1 Mössenböck Vincenz CLA 2011-06-21 04:54:19 EDT
Created attachment 198311 [details]
log
Comment 2 Remy Suen CLA 2011-06-21 08:22:04 EDT
Sounds like something might be wrong with your JRE. I suggest reinstalling your system's JRE.
Comment 3 Oleg Besedin CLA 2011-06-21 10:16:02 EDT
(In reply to comment #2)
> Sounds like something might be wrong with your JRE. I suggest reinstalling your
> system's JRE.

What Remy said.
Comment 4 Francis Upton IV CLA 2011-06-21 10:32:06 EDT
It's missing a crypto class. You might want to google that error to give you a hint. It's possible you don't have a JRE that supports the necessary level of encryption for something.

Also, try it on a new workspace and see if you have the trouble. It could be something in your workspace configuration that's trying to do something your JRE does not like.