Bug 212318 - Dialogs and Wizards not rendering content in Vista 64 bit
Summary: Dialogs and Wizards not rendering content in Vista 64 bit
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 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-07 23:36 EST by Bindul Bhowmik CLA
Modified: 2007-12-11 13:47 EST (History)
3 users (show)

See Also:


Attachments
Screenshot of widget without content (72.40 KB, image/png)
2007-12-07 23:36 EST, Bindul Bhowmik CLA
no flags Details
Screenshot for description in Comment #1 (106.95 KB, image/png)
2007-12-07 23:55 EST, Bindul Bhowmik CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bindul Bhowmik CLA 2007-12-07 23:36:39 EST
Created attachment 84802 [details]
Screenshot of widget without content

Build ID: M20071023-1652

Steps To Reproduce:
1. Update an install of Vista 64 bit ultimate with latest fix packs from Microsoft
2. Get eclipse 3.3.1.1 or 3.3.2 milestone build and create projects
3. New Project, Preferences, External Tools dialogs start loosing content


More information:
I have started seeing this behavior on my eclipse install since the last three days. The dialog boxes for managing external tools, running ant scripts, creating new projects, preferences, etc have stopped rendering partial content on the screen. However, I believe the widgets still think they have all the content. This renders a lot of the widgets completely unusable.

The behavior is random, and does not show up in a new workspace, however once it shows up in a workspace, it sticks. The only way I could make it go away is to create a new workspace.

I checked the workspace logs, and no exceptions are logged there.

I have attached a screenshot of the External Tools widget.

I am running Windows Vista Ultimate 64 bit. I can reproduce this defect on 1.5.0_13 and 1.6.0_03 Sun JVMs. I have tried builds 3.3.1.1 M20071023-1652 and 3.3.2 M20071205-0800 and see the same behavior on both. I have tried running eclipse even with XP SP2 compatibility and can reproduce the problem.

I have my Windows Update service set to auto update, so Windows patches might have been loaded.

I would be more than happy to help in any way to help resolve this problem.
Comment 1 Bindul Bhowmik CLA 2007-12-07 23:47:09 EST
Another related behavior that I have started noticing around the same time as the reported defect is that when restoring a workbench, only a portion of the editor is active, even though the entire editor is visible. To illustrate I have attached a screenshot in which I have drawn a red rectangle. Scrolling or typing in the editor is only possible in the rectangle.

This problem goes away if I maximize and restore the editor.

Randomly I also notice a black area towards the bottom right corner of the editor when the workspace is reopened. Nothing is rendered in that area. Agan that goes away by resizing the editor.
Comment 2 Bindul Bhowmik CLA 2007-12-07 23:55:29 EST
Created attachment 84803 [details]
Screenshot for description in Comment #1

The contents of the editor had to be munged out for confidentiality reasons. The defect is explained in https://bugs.eclipse.org/bugs/show_bug.cgi?id=212318#c1.
Comment 3 Remy Suen CLA 2007-12-09 09:19:18 EST
Please try using 3.4M3. The content-less widget SWT bug is a famous one, see bug 142965 and friends.
Comment 4 Bindul Bhowmik CLA 2007-12-10 00:04:00 EST
(In reply to comment #3)
> Please try using 3.4M3. The content-less widget SWT bug is a famous one, see
> bug 142965 and friends.
> 

I did some testing with 3.4M3, and so far it seems the problem has been fixed. Thank you. I tried the 3.4M3 64bit version so far, I plan to try the 32 bit version later to check that out.

Is there any chance of getting this fix in the 3.3.2 stream? 3.4 release is way out, and it would help tremendously to have the fix in a released version.
Comment 5 Steve Northover CLA 2007-12-11 13:47:06 EST

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