When using  xxxxx  on Win platform with JDK 1.6.0_10,  xxxxx  users reported they got
following NPE from time to time:

Stacktrace: 
java.lang.NullPointerException
        at com.sun.java.swing.plaf.windows.WindowsComboBoxUI$XPComboBoxButton.getState(WindowsComboBoxUI.java:408)
        at com.sun.java.swing.plaf.windows.XPStyle$GlyphButton.paintComponent(XPStyle.java:717)
        at javax.swing.JComponent.paint(JComponent.java:1027)
        at javax.swing.JComponent.paintChildren(JComponent.java:864)
        at javax.swing.JComponent.paint(JComponent.java:1036)
        at javax.swing.JComponent.paintChildren(JComponent.java:864)

Unfortunately, issue is random so I can't give you fully reproducible steps. But by looking at  xxxxx  exception reporter results: http://statistics.netbeans.org/analytics/detail.do?id=11541 we can see that issue is relatively frequent for  xxxxx  users (already 20 duplicates)

Just suggestion - maybe blind null check would be enough to fix this issue?
Posted Date : 2008-08-08 08:51:51.0

I forgot to mention exact JDK build for exception, here it comes:

VM: Java HotSpot(TM) Client VM, 11.0-b11, Java(TM) SE Runtime Environment, 1.6.0_10-beta-b20
OS: Windows XP, 5.1, x86

Original bug filed in NetBeans IZ: http://www.netbeans.org/issues/show_bug.cgi?id=141853
Posted Date : 2008-08-08 08:54:24.0

N/A

It looks like a threading problem in the Netbeans code,
but to be on the safe side we can add a null check for the comboBox field
Posted Date : 2008-08-12 11:33:10.0

I coundn't make a test case to reproduce this bug,
anyway it worth fixing, because the fix is safe and very anticipated by Netbeans
Posted Date : 2008-11-18 15:10:29.0