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 203992 - NullPointerException at org.netbeans.modules.editor.lib2.view.DocumentView.getViewIndex
Summary: NullPointerException at org.netbeans.modules.editor.lib2.view.DocumentView.ge...
Status: RESOLVED DUPLICATE of bug 202588
Alias: None
Product: editor
Classification: Unclassified
Component: Painting & Printing (show other bugs)
Version: 7.1
Hardware: All All
: P3 normal (vote)
Assignee: Miloslav Metelka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-20 08:28 UTC by Marian Petras
Modified: 2011-11-03 13:16 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 181735


Attachments
stacktrace (2.82 KB, text/plain)
2011-10-20 08:28 UTC, Marian Petras
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marian Petras 2011-10-20 08:28:22 UTC
Build: NetBeans IDE 7.1 Beta (Build 201109252201)
VM: Java HotSpot(TM) Server VM, 20.2-b06, Java(TM) SE Runtime Environment, 1.6.0_27-b07
OS: Windows XP

User Comments:
GUEST: I was just working on an XML file....

GUEST: open pom.xml

mpetras: I started the IDE with several fiels open (pom.xml was the active file in the editor view).




Stacktrace: 
java.lang.NullPointerException
   at org.netbeans.modules.editor.lib2.view.DocumentView.getViewIndex(DocumentView.java:327)
   at org.netbeans.modules.editor.lib2.view.ViewHierarchyImpl.modelToParagraphView(ViewHierarchyImpl.java:284)
   at org.netbeans.modules.editor.lib2.view.LockedViewHierarchy.modelToParagraphView(LockedViewHierarchy.java:124)
   at org.netbeans.editor.GlyphGutter$6.run(GlyphGutter.java:655)
   at org.netbeans.editor.BaseDocument.render(BaseDocument.java:1404)
   at org.netbeans.editor.GlyphGutter.changedLine(GlyphGutter.java:644)
Comment 1 Marian Petras 2011-10-20 08:28:26 UTC
Created attachment 112244 [details]
stacktrace
Comment 2 Miloslav Metelka 2011-11-03 13:16:15 UTC
This is likely caused by incorrect locking resolved in terms of issue 202588.
Please use a recent dev build. If the problem would persist please reopen the issue.

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