Bug 35263 - Eclipse crashes when opening Hierarchy view for java.lang.Eception
Summary: Eclipse crashes when opening Hierarchy view for java.lang.Eception
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 major (vote)
Target Milestone: 3.0 M1   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-18 18:16 EST by Michael Erdmann CLA
Modified: 2016-07-21 09:54 EDT (History)
1 user (show)

See Also:

Attachments
error info box after crash in PNG format (6.28 KB, image/png)
2003-03-18 18:18 EST, Michael Erdmann CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Erdmann CLA 2003-03-18 18:16:51 EST 
When right clicking in the editor on the text Exception and
selecting "open type hiererchy" crashes Eclipse.
The hierarchy building process works a while (3-5 sec) and then 
Eclipse crashes with exit code=128.

I am using Version: 2.1.0 Build id: 200303071024 on Windows 2000.
Comment 1 Michael Erdmann CLA 2003-03-18 18:18:17 EST 
Created attachment 4229 [details]
 error info box after crash in PNG format
Comment 2 Jerome Lanneluc CLA 2003-03-19 02:55:23 EST 
Sounds like you're having a VM problem. Can you reproduce with another VM?
Comment 3 Philipe Mulet CLA 2003-03-19 17:51:41 EST 
Closing. Please reopen if you can reproduce on a different VM, some 1.3.1 VMs 
are known to be defective.
Comment 4 Michael Erdmann CLA 2003-03-21 14:20:34 EST 
I can reproduce this exact same bahaviour using Suns VM that comes with 
JDK 1.3.1 and JDK 1.3.1_07. If you cannot reprcoduce it please send me
the VM version you are using and I can try that one. Which of the 1.4's
is stable?
Comment 5 Philipe Mulet CLA 2003-03-22 04:36:32 EST 
Please try with Sun 1.4.1_01. 
Also did you give Eclipse enough memory ? (-Xmx256MB)
Comment 6 Michael Erdmann CLA 2003-03-24 13:54:53 EST 
I tried to unvoke eclipse like this:
  eclipse.exe -data c:\eclipse-Workspace -vmargs -Xmx256MB -Xss1024k

Still the same problem.

Are there some lock files you need to see? Or some other startup parameters
I shoud specify?
Comment 7 Philipe Mulet CLA 2003-03-24 16:39:17 EST 
Did you specify the -vm <path to java.exe> argument ? 
Did you also check the workspace/.metadata/.log file ?
Can you reproduce also with a more recent integration build ?
Comment 8 Philipe Mulet CLA 2003-04-01 04:47:02 EST 
Michael - can you still reproduce or is it ok to close ?
Comment 9 Michael Erdmann CLA 2003-04-03 13:08:00 EST 
the bug is still there even if I follow your suggestions of using the lates
builds and JDK 1.4.1.

But I just found out that the reason for this misbehaviour is my WORKSPACE.
I have been using it for several months. I was referring to it by
  -data c:\eclipse-Workspace

If I remove it from my eclipse start script everything works fine.
Thus , I will mark the bug as invalid.