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 37278 - NullPointerException TextEditorComponent
Summary: NullPointerException TextEditorComponent
Status: VERIFIED WORKSFORME
Alias: None
Product: xml
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: Petr Pisl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-17 14:29 UTC by ender01
Modified: 2007-11-23 16:51 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
ide log file (280.01 KB, text/plain)
2003-11-17 14:31 UTC, ender01 		Details
exception that is thrown on startup (1.21 KB, text/plain)
2003-11-17 14:45 UTC, ender01 		Details
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 ender01 2003-11-17 14:29:17 UTC 
Trying to edit a xml file while it is maximazied 
causes NetBeans to lock up. Then when trying 
restart the IDE I get the attached stack trace. 
Also attached is the ide.log file.
Comment 1 ender01 2003-11-17 14:31:50 UTC 
Created attachment 12177 [details]
ide log file
Comment 2 ender01 2003-11-17 14:45:58 UTC 
Created attachment 12178 [details]
exception that is thrown on startup
Comment 3 ender01 2003-11-17 14:48:26 UTC 
Can re-create by doing the following:
Open up an xml file. Then open any other file (only tested with .java 
files) and make to view panes in the text editor. Make sure the xml 
file is saved (no * by its name) then maximize the xml file, and try 
to edit it. What happens here is that the texteditor freezes up, but I 
can still close the IDE. After the IDE is closed, reboot and try to 
start it again, and the exception is thrown.
Comment 4 Martin Roskanin 2003-11-18 16:21:37 UTC 
It seems to be issue of xml module. Reassigning.
Comment 5 Petr Pisl 2004-02-19 13:04:50 UTC 
I am  not able to reproduce this behavior. I close the bug as works
for me. If you have still this problem, please reopen the bug and
write up me how reproduce.
Comment 6 ender01 2004-02-19 13:58:53 UTC 
It appears the problem has gone away. I cant reproduce it either in 
the latest beta release.
Comment 7 Mikhail Matveev 2007-11-23 16:51:56 UTC 
Seems to be fixed long time ago