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 42011 - NPE in emtpy output window when selecting > 2 lines
Summary: NPE in emtpy output window when selecting > 2 lines
Status: RESOLVED FIXED
Alias: None
Product: cnd
Classification: Unclassified
Component: Terminalemulator (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: ivan
URL:
Keywords:
Depends on: 28297
Blocks:
  Show dependency tree
 
Reported: 2004-04-15 08:56 UTC by tomzi
Modified: 2008-12-23 08:42 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description tomzi 2004-04-15 08:56:35 UTC 
When selecting at least to lines in an emtpy
output window and moving it out of sight a NPE occurs.

Details:
.) Open output window
.) Clear Output
.) Select at least two lines in the emtpy area
.) Move the bottom area out of sight using
horizontal window dividers.

When the window reaches the selected lines a popup
with a NPE occurs:

java.lang.NullPointerException
	at
org.netbeans.lib.terminalemulator.Buffer.visitLines(Buffer.java:195)
	at
org.netbeans.lib.terminalemulator.Term.visitLines(Term.java:832)
	at
org.netbeans.lib.terminalemulator.Sel.paint(Sel.java:426)
	at
org.netbeans.lib.terminalemulator.Term.do_paint(Term.java:2828)
	at
org.netbeans.lib.terminalemulator.Screen.paint(Screen.java:143)
	at
javax.swing.JComponent.paintChildren(JComponent.java:647)
	at javax.swing.JComponent.paint(JComponent.java:817)
	at
javax.swing.JComponent.paintChildren(JComponent.java:647)
	at javax.swing.JComponent.paint(JComponent.java:817)
	at
javax.swing.JComponent.paintWithOffscreenBuffer(JComponent.java:4795)
	at
javax.swing.JComponent.paintDoubleBuffered(JComponent.java:4748)
	at
javax.swing.JComponent._paintImmediately(JComponent.java:4692)
	at
javax.swing.JComponent.paintImmediately(JComponent.java:4495)
	at
javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:410)
[catch] at
javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEventQueueUtilities.java:117)
	at
java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
	at
java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
	at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
	at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
	at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
	at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
	at
java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
Comment 1 _ tboudreau 2004-04-19 14:06:43 UTC 
Reassigning to Marek, new owner of output window and help system
Comment 2 Marian Mirilovic 2006-09-25 10:50:39 UTC 
The core team has not been responsible for terminal emulator for long time, so
reassigne all opened issues to responsible person.
Comment 3 tomzi 2007-06-15 09:50:46 UTC 
Seems to work now.
Comment 4 ivan 2007-06-15 19:28:50 UTC 
terminalemulator was a building block of the older outputwindow.
The current output window (output2) doesn't use term.
it's likely that the problem still exists in term, but
not in output2.
Comment 5 Quality Engineering 2008-12-23 08:42:15 UTC 
moving terminal emulator issues to terminalemulator component.
To see the correct version and target milestone of this issue look at Issue
Activity table.