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 209712 - java.io.IOException: Cannot parse configuration of window manager MultiFileObject@1556bda[Windows2Local/WindowManager.wswmgr]
Summary: java.io.IOException: Cannot parse configuration of window manager MultiFileOb...
Status: RESOLVED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 7.1
Hardware: All All
: P3 normal (vote)
Assignee: Stanislav Aubrecht
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-19 02:02 UTC by minashokry
Modified: 2014-02-21 06:29 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 181752


Attachments
stacktrace (2.61 KB, text/plain)
2012-03-19 02:02 UTC, minashokry
Details

Note You need to log in before you can comment on or make changes to this bug.
Description minashokry 2012-03-19 02:02:50 UTC
Build: NetBeans IDE 7.1 (Build 201112071828)
VM: OpenJDK 64-Bit Server VM, 21.0-b17, OpenJDK Runtime Environment, 1.7.0_147-icedtea-b147
OS: Linux

User Comments:
GUEST: i don't remember

mklaehn: happened during during or right after startup of netbeans




Stacktrace: 
org.xml.sax.SAXParseException; lineNumber: 78667; columnNumber: 1002; An invalid XML character (Unicode: 0x0) was found in the element content of the document.
   at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198)
   at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
   at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:441)
   at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368)
   at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1375)
   at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2854)
Comment 1 minashokry 2012-03-19 02:02:53 UTC
Created attachment 116837 [details]
stacktrace
Comment 2 Martin Entlicher 2012-04-06 08:05:31 UTC
Most of the reports belong to Window system.
In Logger, we have enough of reports like this already, so do not pass back.

I've found, that some of such problems (if not all of them) were caused by incomplete writes, when there was no more space left on the device.
In an attempt to solve this, I've created DataConsistentFileOutputStream
http://hg.netbeans.org/main/rev/a4804ab38877
If you think this is a good idea, we can make an API from this...
Comment 3 Stanislav Aubrecht 2012-04-06 09:22:16 UTC
(In reply to comment #2)
> Most of the reports belong to Window system.
> In Logger, we have enough of reports like this already, so do not pass back.
> 
> I've found, that some of such problems (if not all of them) were caused by
> incomplete writes, when there was no more space left on the device.
> In an attempt to solve this, I've created DataConsistentFileOutputStream
> http://hg.netbeans.org/main/rev/a4804ab38877
> If you think this is a good idea, we can make an API from this...

I'm not sure it would help anything. When the window system is being saved the main window is no longer visible. Any IO exceptions would be just lost in the log file and the next start of the IDE would fail with the same error...
Comment 4 Stanislav Aubrecht 2012-04-11 15:08:44 UTC
The exception report from org.netbeans.lib.uihandler.LogRecords.scan got mixed up with windows system exceptions so I've removed that one from the list.

There is actually nothing to fix here - window system detects a problem in stored data (possibly corrupt user dir, e.g. due to low disk space) and falls back to the default configuration.
Comment 5 swpalmer 2014-02-17 20:57:00 UTC
My error report #712848 was marked as a duplicate of #181752 and that this was the corresponding bug.

However, I launched with a clean user dir (first launch since uninstalling previous dev build and deleting the user dir) and I have plenty of free space on the device.
Since I encountered this with the latest available NB 8.0 dev build at the time (201402170649) and the remarks about low disk space don't apply, I suggest re-opening this issue.
Comment 6 Stanislav Aubrecht 2014-02-18 09:09:41 UTC
(In reply to swpalmer from comment #5)
> My error report #712848 was marked as a duplicate of #181752 and that this
> was the corresponding bug.
> 
> However, I launched with a clean user dir (first launch since uninstalling
> previous dev build and deleting the user dir) and I have plenty of free
> space on the device.
> Since I encountered this with the latest available NB 8.0 dev build at the
> time (201402170649) and the remarks about low disk space don't apply, I
> suggest re-opening this issue.

In your case the exception comes from org.netbeans.modules.editor.options.AnnotationTypeProcessor class and not from the window system.
You may want to file a new bug.
Comment 7 MackSix 2014-02-21 06:29:37 UTC
(In reply to Stanislav Aubrecht from comment #6)
> (In reply to swpalmer from comment #5)
> > My error report #712848 was marked as a duplicate of #181752 and that this
> > was the corresponding bug.
> > 
> > However, I launched with a clean user dir (first launch since uninstalling
> > previous dev build and deleting the user dir) and I have plenty of free
> > space on the device.
> > Since I encountered this with the latest available NB 8.0 dev build at the
> > time (201402170649) and the remarks about low disk space don't apply, I
> > suggest re-opening this issue.
> 
> In your case the exception comes from
> org.netbeans.modules.editor.options.AnnotationTypeProcessor class and not
> from the window system.
> You may want to file a new bug.

I have identical exception in log file. I filed it here: Issue 242179