Bug 211098 - "Java Build Path" missing all tabs
Summary: "Java Build Path" missing all tabs
Status: RESOLVED DUPLICATE of bug 142965
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.3.1   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-27 13:19 EST by LeonChen Mising name CLA
Modified: 2007-11-29 12:02 EST (History)
2 users (show)

See Also:

Attachments
Broken "Java Build Path" (40.35 KB, image/png)
2007-11-27 13:19 EST, LeonChen Mising name 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 LeonChen Mising name CLA 2007-11-27 13:19:09 EST 
Created attachment 83888 [details]
Broken "Java Build Path"

I am using Eclipse 3.3, start it using the command:
D:\eclipse3.3\eclipse.exe -vm D:\jdk1.6.0_03\bin\javaw.exe -vmargs -Xmx900m -XX:MaxPermSize=90m

After the IDE started, when I clicked the "Java Build Path" 2nd times (1st is normal),  all tabs in the "Java Build Path" was missing...
Please see the attachment.

I have to restart Eclipse to bring tabs of "Java Build Path" back.

Please help me, thanks!
Comment 1 Remy Suen CLA 2007-11-28 08:08:41 EST 
Are you using the 32-bit Window or the 64-bit Windows?
Comment 2 LeonChen Mising name CLA 2007-11-28 08:40:59 EST 
(In reply to comment #1)
> Are you using the 32-bit Window or the 64-bit Windows?
I am using 64-bits Vista, thanks!
Comment 3 Remy Suen CLA 2007-11-28 09:37:16 EST 
(In reply to comment #2)
> I am using 64-bits Vista, thanks!

Please try using Eclipse 3.4M3 instead. Things "going missing" is a well-known problem on 64-bit Windows, see bug 142965 and its many other duplicates.
Comment 4 Steve Northover CLA 2007-11-28 23:05:40 EST 
Looks like a dup of the famous Windows WM_SIZE limit.
Comment 5 Grant Gayed CLA 2007-11-29 10:03:41 EST 
Yes, this is very likely a duplicate that is now fixed.  If 3.4M3 does not help you then please reopen this report.


*** This bug has been marked as a duplicate of bug 142965 ***
Comment 6 LeonChen Mising name CLA 2007-11-29 12:02:17 EST 
Ya, after upgrading to 3.4M3, the problem is solved! thanks!