JDK-4463500 : ColorChooser Demo in the SwingSet 2 Demo does not repaint correctly on Dual CPUs
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 1.4.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_nt,windows_xp
  • CPU: x86
  • Submitted: 2001-05-27
  • Updated: 2005-03-16
  • Resolved: 2004-09-14
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6 betaFixed
Related Reports
Duplicate :  
Relates :  
Relates :  
Description

Name: krC82822			Date: 05/26/2001


java version "1.4.0-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta-b65)
Java HotSpot(TM) Client VM (build 1.4.0-beta-b65, mixed mode)

The ColorChooser Demo of the Swing Set 2 Demo does not repaint
correctly if executed on a dual processor system. If the processor
affinty of the processor is set to a single CPU, the demo repaints
correctly.
(Review ID: 125072) 
======================================================================

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mustang FIXED IN: mustang INTEGRATED IN: mustang
14-09-2004

EVALUATION Need to find a dual processor machine to test this on. ###@###.### 2001-11-16 Name: apR10262 Date: 11/20/2003 The bug is appeared when the panel is repainted during the image generating process. This is possible because of lack of synchronization between the image generating thread and the main thread ====================================================================== The fix to this bug may have caused a regression in the ColorChooser demo. See new bug 5008179. ###@###.### 2004-03-04 Good news: 5008179 has been closed as not reproducible as a result of the fix for 4967886. No further issues are apparent. ###@###.### 2005-03-16 18:57:28 GMT
04-03-2004