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 19687 - NPE while externalizing tree component without support
Summary: NPE while externalizing tree component without support
Status: CLOSED FIXED
Alias: None
Product: xml
Classification: Unclassified
Component: Tree-Edit (show other bugs)
Version: 3.x
Hardware: PC All
: P3 blocker (vote)
Assignee: _ lkramolis
URL:
Keywords:
Depends on: 19855
Blocks:
  Show dependency tree
 
Reported: 2002-01-23 10:27 UTC by _ pkuzel
Modified: 2007-09-25 06:06 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
hang after windows are opened... (41.12 KB, text/plain)
2002-01-23 23:48 UTC, Phil Sager
Details
Patch (927 bytes, patch)
2002-01-24 18:43 UTC, _ pkuzel
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description _ pkuzel 2002-01-23 10:27:40 UTC
I have the NullPointerException when trying to close it.  I am running
Linux 2.4.16 (SuSE 7.1) with Blackdown JDK 1.3.1-02 on a machine with
512M memory.  I downloaded the RC2 tarball and put it to its own
directory, made a copy of my RC1 user directory, and started like this:

/opt/netbeans-3.3.1-RC2/bin/runide.sh \
-jdkhome /usr/lib/java \
-userdir /home/glennh/nbuser331-RC2 \
-J-Xmx256M -J-Xincgc -J-Xverify:none

Immediately it opened, I closed the main window (MDI) and got the
exception.  NetBeans would not die, I had to shoot it.  Here is the
trace from the error dialog:

Tue Jan 22 16:44:57 CST 2002: java.lang.NullPointerException: <no message>
java.lang.NullPointerException
   at
org.netbeans.modules.xml.tree.editor.TreeEditorComponent.writeExternal(TreeEditorComponent.java:282)
   at
org.openide.windows.TopComponent$Replacer.writeObject(TopComponent.java:737)
   at java.lang.reflect.Method.invoke(Native Method)
   at
java.io.ObjectOutputStream.invokeObjectWriter(ObjectOutputStream.java:1864)
   at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1210)
   at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
   at
org.openide.loaders.XMLSettingsSupport.storeSerialData(XMLSettingsSupport.java:145)
   at
org.openide.loaders.XMLSettingsSupport.storeToXML10(XMLSettingsSupport.java:82)
   at
org.openide.loaders.InstanceDataObject$SettingsInstance.saveInstance2Buffer(InstanceDataObject.java:1505)
   at
org.openide.loaders.InstanceDataObject$SettingsInstance.access$200(InstanceDataObject.java:1132)
   at
org.openide.loaders.InstanceDataObject.storeSettings(InstanceDataObject.java:329)
   at
org.openide.loaders.InstanceDataObject.access$1700(InstanceDataObject.java:66)
   at
org.openide.loaders.InstanceDataObject$Creator.run(InstanceDataObject.java:1728)
   at org.openide.filesystems.EventControl.runAtomicAction(EventControl.java:89)
   at org.openide.filesystems.FileSystem.runAtomicAction(FileSystem.java:388)
   at
org.openide.loaders.InstanceDataObject$Creator.createInstanceDataObject(InstanceDataObject.java:1743)
   at org.openide.loaders.InstanceDataObject.create(InstanceDataObject.java:318)
   at
org.netbeans.core.windows.PersistenceManager.forceSaveOfTopComponents(PersistenceManager.java:493)
   at
org.netbeans.core.windows.PersistenceManager.writeXML(PersistenceManager.java:249)
   at org.netbeans.modules.projects.PSupport.projectSave(PSupport.java:223)
   at
org.netbeans.core.NbProjectOperation.storeLastProject(NbProjectOperation.java:52)
   at org.netbeans.core.NbTopManager.exit(NbTopManager.java:698)
   at org.netbeans.core.actions.SystemExit.performAction(SystemExit.java:54)
   at org.netbeans.core.windows.MainWindow$3.windowClosing(MainWindow.java:155)
   at java.awt.AWTEventMulticaster.windowClosing(AWTEventMulticaster.java:291)
   at java.awt.AWTEventMulticaster.windowClosing(AWTEventMulticaster.java:290)
   at java.awt.Window.processWindowEvent(Window.java:812)
   at javax.swing.JFrame.processWindowEvent(JFrame.java:237)
   at
org.netbeans.core.windows.MainWindow.processWindowEvent(MainWindow.java:366)
   at java.awt.Window.processEvent(Window.java:788)
   at java.awt.Component.dispatchEventImpl(Component.java:2593)
[catch] at java.awt.Container.dispatchEventImpl(Container.java:1213)
   at java.awt.Window.dispatchEventImpl(Window.java:926)
   at java.awt.Component.dispatchEvent(Component.java:2497)
   at java.awt.EventQueue.dispatchEvent(EventQueue.java:339)
   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)


Just do not know how to reproduce it.
Comment 1 Phil Sager 2002-01-23 23:47:00 UTC
Symptoms on my machine were NB hanging after opening all windows. I 
read the mail thread that pointed to this bug report and checked out 
my ide.log. The system stopped while loading xml modules. Disabled 
xml rc-2 and have been running okay since. I am attaching the ide.log 
in case it is useful..
Comment 2 Phil Sager 2002-01-23 23:48:10 UTC
Created attachment 4366 [details]
hang after windows are opened...
Comment 3 _ pkuzel 2002-01-24 18:43:35 UTC
Created attachment 4406 [details]
Patch
Comment 4 _ pkuzel 2002-01-24 18:47:02 UTC
Phil on hang-ups please attach Thread dumps (Ctrl+Break) instead of
log.

Anyway I workarounded hang up on IDE exit.
Comment 5 _ pkuzel 2002-01-25 11:01:39 UTC
High resistance mode integration approvers, could you please approve
integration into release33 branch?

Thanks a lot.
Comment 6 eadams 2002-01-25 12:18:59 UTC
Ian and I discussed this and we approve.

If XML was part of the NB 3.3.1 release we would not
approve this P3, however, it isn't part of NB 3.3.1.
Comment 7 Martin Balin 2002-01-25 12:21:18 UTC
Approved.
Comment 8 _ pkuzel 2002-01-28 10:39:35 UTC
Integrated into release33 branch.
Comment 9 tboerkel 2002-01-29 08:43:10 UTC
Apparently, this is not fixed in 3.3.1 build 200201290331.
Comment 10 _ pkuzel 2002-02-01 13:24:45 UTC
Thomas, the workaround is a part of XML module. You must use XML
module RC3 that is scheduled to be released today. If you can
reproduce it with XML module RC3 release then reopen this bug.
Comment 11 _ lkramolis 2002-02-14 17:16:02 UTC
Reverse problem described in issue 20487.
Comment 12 Martin Schovanek 2002-07-24 14:31:10 UTC
VERIFIED
Comment 13 Quality Engineering 2003-07-02 08:39:22 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.