This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 161942 - NullPointerException at javax.swing.OverlayLayout.preferredLayoutSize
Summary: NullPointerException at javax.swing.OverlayLayout.preferredLayoutSize
Status: RESOLVED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: mslama
URL: http://statistics.netbeans.org/except...
Keywords:
: 161943 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-04-04 01:40 UTC by kayvan
Modified: 2009-04-10 14:37 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 148881


Attachments
stacktrace (3.83 KB, text/plain)
2009-04-04 01:40 UTC, kayvan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kayvan 2009-04-04 01:40:44 UTC
Build: NetBeans IDE 6.5 (Build 200811100001)
VM: Java HotSpot(TM) Client VM, 10.0-b19, Java(TM) SE Runtime Environment, 1.6.0_05-b13
OS: Windows XP, 5.1, x86

Stacktrace: 
java.lang.NullPointerException
        at javax.swing.OverlayLayout.preferredLayoutSize(OverlayLayout.java:121)
        at java.awt.Container.preferredSize(Container.java:1616)
        at java.awt.Container.getPreferredSize(Container.java:1601)
        at javax.swing.JComponent.getPreferredSize(JComponent.java:1634)
        at javax.swing.ScrollPaneLayout.layoutContainer(ScrollPaneLayout.java:769)
        at java.awt.Container.layout(Container.java:1432)
Comment 1 kayvan 2009-04-04 01:40:49 UTC
Created attachment 79425 [details]
stacktrace
Comment 2 Stanislav Aubrecht 2009-04-04 15:48:01 UTC
*** Issue 161943 has been marked as a duplicate of this issue. ***
Comment 3 mslama 2009-04-10 14:37:15 UTC
2 reports from NB 6.5 and no further report from dev build till now. No idea if it could be some race condition or some
problem in Swing. Without more info or steps to reproduce at least more often we cannot diagnose problem. I also did not
find any such report in JDK bug database.