JDK-4881422 : repaint causes problems on multi-head configuration
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Cannot Reproduce
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2003-06-19
  • Updated: 2005-08-16
  • Resolved: 2005-08-16
Related Reports
Relates :  
Description
This problem is seen on an application which uses several Swing/AWT windows on a multi-head display.  The customer typically starts up 3 instances of their application and puts one instance in each screen.  When they do something un-related to the application, such as bringing up Windows Explorer, the entire Java application repaints, causing the screen to flicker and a very unpleasant visual effect for their users.

The customer is using 1.4.0_01 and 1.4.0_03 on Windows 2000 SP2.   Other Windows platforms have not been tested.  The application typically runs on a system with 3 monitors and a multi-head grahics card, such as the Matrox G200 MMS (2,4) 32 MB. The problem can be seen with a single display, but it is not nearly as obvious or reproducible.

A stack trace taken by the customer at the time of a repaint is attached.

Comments
EVALUATION Related bug 4905270 was escalated (#547658), so this problem has been addressed for 1.4.* releases. ###@###.### 2003-10-21 I haven't been able to reproduce this bug on my system (P4 2.8 HT, dual ATI Radeon 9600, Win XP SP1) with current Mustang workspace, Tiger and 1.4.2 using simple Java applications like SwingSet. So we need a test from the customer to see if the bug still can be reproduced or not. I suspect that the bug may have been already fixed by some other paint-related fixes, so it would be useful the customer to test the application with 5.0 or latest 6.0 builds. I'm marking the bug as incomplete until some more information is provided. ###@###.### 2005-06-28 12:54:50 GMT
28-06-2005

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mustang
23-09-2004

WORK AROUND The flicker occurs less often if the display mode is changed from 32-bit to 16-bit, or if swing.volatileImageBufferEnabled is set to false.
23-09-2004