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 246756

Summary: Netbeans gui broken after closing embedded browser window
Product: platform Reporter: everflux <everflux>
Component: Window SystemAssignee: Stanislav Aubrecht <saubrecht>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: P2    
Version: 8.0.1   
Hardware: PC   
OS: Linux   
Issue Type: DEFECT Exception Reporter:
Attachments: netbeans messages

Description everflux 2014-08-28 16:05:40 UTC
Created attachment 148941 [details]
netbeans messages

I launched a Java EE project in Tomcat with embedded webkit window, then clicked 'close'.
Netbeans GUI is broken/unresponsive afterwards. I could not even use the exception reporter.

java version "1.8.0_20"
Java(TM) SE Runtime Environment (build 1.8.0_20-b26)
Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode)
Comment 1 everflux 2014-08-28 16:06:22 UTC
Product Version: NetBeans IDE 8.0.1 (Build 201408142300)
Comment 2 Marian Mirilovic 2014-09-02 16:45:15 UTC
java.lang.NullPointerException
	at org.netbeans.core.windows.view.ViewHelper.setSplitWeights(ViewHelper.java:250)
	at org.netbeans.core.windows.view.DefaultView.userMovedSplit(DefaultView.java:780)
	at org.netbeans.core.windows.view.SplitView$1.propertyChange(SplitView.java:198)
	at java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:335)
	at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:328)
	at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:263)
	at java.awt.Component.firePropertyChange(Component.java:8422)
	at org.netbeans.core.windows.view.ui.MultiSplitPane.access$400(MultiSplitPane.java:82)
	at org.netbeans.core.windows.view.ui.MultiSplitPane$MultiSplitLayout.layoutContainer(MultiSplitPane.java:674)
	at java.awt.Container.layout(Container.java:1508)
Comment 3 Stanislav Aubrecht 2014-09-03 07:50:55 UTC

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