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 28772 - ide crashed
Summary: ide crashed
Status: CLOSED DUPLICATE of bug 28307
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: Peter Zavadsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-11-15 09:40 UTC by Bogdan Mizerski
Modified: 2008-12-23 09:22 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bogdan Mizerski 2002-11-15 09:40:46 UTC
*********** Exception occurred ************ at Fri Nov 15 
10:24:54 CET 2002
java.lang.NullPointerException
	at javax.swing.DefaultDesktopManager.maximizeFrame
(DefaultDesktopManager.java:81)
	at 
javax.swing.plaf.basic.BasicInternalFrameUI.maximizeFrame
(BasicInternalFrameUI.java:607)
	at 
javax.swing.plaf.basic.BasicInternalFrameUI$InternalFramePr
opertyChangeListener.propertyChange
(BasicInternalFrameUI.java:423)
	at 
javax.swing.event.SwingPropertyChangeSupport.firePropertyCh
ange(SwingPropertyChangeSupport.java:161)
	at 
javax.swing.event.SwingPropertyChangeSupport.firePropertyCh
ange(SwingPropertyChangeSupport.java:130)
	at javax.swing.JComponent.firePropertyChange
(JComponent.java:3208)
	at javax.swing.JInternalFrame.setMaximum
(JInternalFrame.java:890)
	at 
org.netbeans.core.windows.frames.InternalFrameTypeImpl.setM
aximum(InternalFrameTypeImpl.java:356)
	at 
org.netbeans.core.windows.frames.InternalFrameTypeImpl.setS
tate(InternalFrameTypeImpl.java:272)
	at org.netbeans.core.windows.ModeImpl.setFrameState
(ModeImpl.java:1258)
	at 
org.netbeans.core.windows.layers.ModeData$CookiesImpl.setPr
ops2Mode(ModeData.java:626)
	at 
org.netbeans.core.windows.layers.ModeData$CookiesImpl.updat
eProperties(ModeData.java:496)
	at 
org.netbeans.core.windows.layers.ModeData$CookiesImpl.updat
eAll(ModeData.java:415)
	at 
org.netbeans.core.windows.layers.ModeData$CookiesImpl.loadD
ataSection(ModeData.java:1239)
	at 
org.netbeans.core.windows.ModeImpl.ensureSectionLoaded
(ModeImpl.java:2373)
	at 
org.netbeans.core.windows.ModeImpl.doGetTopComponents
(ModeImpl.java:885)
	at 
org.netbeans.core.windows.ModeImpl.getTopComponents
(ModeImpl.java:872)
	at 
org.openide.text.CloneableEditor.openOnOtherWorkspaces
(CloneableEditor.java:748)
	at org.openide.text.CloneableEditor.open
(CloneableEditor.java:253)
	at org.openide.windows.TopComponent.open
(TopComponent.java:188)
	at 
org.openide.windows.CloneableOpenSupport.openCloneableTopCo
mponent(CloneableOpenSupport.java:163)
	at org.openide.windows.CloneableOpenSupport$1.run
(CloneableOpenSupport.java:71)
	at java.awt.event.InvocationEvent.dispatch
(InvocationEvent.java:154)
	at java.awt.EventQueue.dispatchEvent
(EventQueue.java:337)
[catch] at 
java.awt.EventDispatchThread.pumpOneEventForHierarchy
(EventDispatchThread.java:131)
	at 
java.awt.EventDispatchThread.pumpEventsForHierarchy
(EventDispatchThread.java:98)
	at java.awt.EventDispatchThread.pumpEvents
(EventDispatchThread.java:93)
	at java.awt.EventDispatchThread.run
(EventDispatchThread.java:85)
Comment 1 pzajac 2002-11-15 12:10:56 UTC
Bogdan, 
can you explain your problem? We don't know your IDE version (build),
jdk version. I see only exception in Swing. I cannot understand what
do you mean by "ide crashed". Can you reproduce this bug?
Comment 2 pzajac 2002-11-15 17:04:45 UTC
bmizerski has send me the messeage: 

My version of NetBeans is 3.4, java j2sdk 4.0_01, system Win 2000 prof.

At first, I saw this message and NetBeans was broken. After that, I
restarted system and all work OK. It was 5'th crash at this day.

At this moment, NetBeans is working OK, only after F1, I have message:
Annotation: Could not connect to URL
nbdocs:/org/netbeans/modules/db/docs/JavaHelpSearch2/SCHEMA; no such
resource was found.
org.netbeans.core.execution.ExitSecurityException: Illegal attempt to exit
early.

it seems as problem in db module.
Comment 3 Peter Zavadsky 2002-12-02 13:55:56 UTC

*** This issue has been marked as a duplicate of 28307 ***