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 18090 - Exception occured in beta 5 (not in beta4) during saving
Summary: Exception occured in beta 5 (not in beta4) during saving
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: Marian Petras
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-26 16:55 UTC by Andreas Schoerk
Modified: 2001-12-18 15:54 UTC (History)
0 users

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 Andreas Schoerk 2001-11-26 16:55:18 UTC
Hello,
This occured when I tried to save one specific file.
At this moment I can´t reproduce it.
But it occured two times so I think it is a common bug
Andreas

Sun Nov 25 08:15:55 CET 2001: java.lang.NullPointerException: null

java.lang.NullPointerException

	at org.netbeans.modules.debugger.support.java.BreakpointUpdater.dispose(BreakpointUpdater.java:178)

	at org.netbeans.modules.debugger.support.java.JavaLineBreakpointEvent.dispose(JavaLineBreakpointEvent.java:124)

	at org.netbeans.modules.debugger.multisession.SessionBreakpoint.disposeEvents(SessionBreakpoint.java:224)

	at org.netbeans.modules.debugger.multisession.SessionBreakpoint.setBreakpoint(SessionBreakpoint.java:111)

	at org.netbeans.modules.debugger.multisession.SessionBreakpoint.fireEventPropertyChange(SessionBreakpoint.java:170)

	at org.netbeans.modules.debugger.CoreBreakpoint$Event.firePropertyChange(CoreBreakpoint.java:535)

	at org.netbeans.modules.debugger.support.java.JavaLineBreakpointEvent.sourceModified(JavaLineBreakpointEvent.java:440)

	at org.netbeans.modules.debugger.support.java.JavaLineBreakpointEvent$LineBreakpointUpdater.fileChanged(JavaLineBreakpointEvent.java:536)

	at org.openide.filesystems.FileObject$ED.dispatch(FileObject.java:630)

	at org.openide.filesystems.FileSystem$EventDispatcher.dispatch(FileSystem.java:675)

	at org.openide.filesystems.FileSystem$EventDispatcher.run(FileSystem.java:671)

	at org.openide.filesystems.EventControl.dispatchEvent(EventControl.java:47)

	at org.openide.filesystems.FileSystem.dispatchEvent(FileSystem.java:418)

	at org.openide.filesystems.FileObject.dispatchEvent(FileObject.java:366)

	at org.openide.filesystems.FileObject.fireFileChangedEvent(FileObject.java:331)

	at org.openide.filesystems.AbstractFolder.fileChanged0(AbstractFolder.java:491)

	at org.openide.filesystems.AbstractFolder.outputStreamClosed(AbstractFolder.java:817)

	at org.openide.filesystems.AbstractFileObject.outputStreamClosed(AbstractFileObject.java:741)

	at org.openide.filesystems.StreamPool.closeOutputStream(StreamPool.java:181)

	at org.openide.filesystems.StreamPool.access$000(StreamPool.java:34)

	at org.openide.filesystems.StreamPool$NotifyOutputStream.close(StreamPool.java:239)

	at java.io.FilterOutputStream.close(FilterOutputStream.java:146)

	at org.openide.text.CloneableEditorSupport.saveDocument(CloneableEditorSupport.java:392)

	at org.openide.text.EditorSupport$Del.superSaveDocument(EditorSupport.java:749)

	at org.openide.text.EditorSupport.saveDocument(EditorSupport.java:260)

	at org.netbeans.modules.java.JavaEditor.saveDocument(JavaEditor.java:386)

	at org.netbeans.modules.java.JavaEditor.saveDocument(JavaEditor.java:368)

	at org.openide.text.EditorSupport$EntryEnv.save(EditorSupport.java:848)
Comment 1 Jan Lahoda 2001-11-26 20:20:30 UTC
So, there is no editor in stack trace, and the first from top is
debugger, so passing to debugger.
Comment 2 Jan Chalupa 2001-11-27 12:09:17 UTC
Target milestone -> 3.3.1.
Comment 3 Marian Petras 2001-11-27 20:25:12 UTC
Fixed in branch 'release33' and in the main trunk.

I was not able to reproduce it but I believe it has happened. I have
made a fix which should prevent the exception. It still may write a
short warning into a log file in some cases but it does not affect
functionality.
Comment 4 Jan Jancura 2001-11-28 13:56:58 UTC
If this bug is really fixed, there should not be any "short warning
". So fix it, please or do not write anything to a log file .
Comment 5 Marian Petras 2001-11-28 18:43:09 UTC
Fixed in branch 'release33'.
Comment 6 Marian Petras 2001-11-28 22:37:45 UTC
Fixed also in the main trunk.
Comment 7 Marian Petras 2001-11-29 15:43:02 UTC
The exception is thrown if method 'dispose()' is called multiple times
on a single breakpoint. Multiple calls did not cause any problems
until class 'BreakpointUpdater' was added. Method
'BreakpointUpdater.dispose()' expected that it is called just once per
a single breakpoint.

A fix integrated into the main trunk and to branch 'release33' assures
both that 'dispose()' is called just once plus it makes
'BreakpointUpdater.dispose()' resistant to multiple calls.
Comment 8 Marian Petras 2001-11-30 14:30:34 UTC
Fixed also in branch 'release330'.