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 122708 - java.lang.NullPointerException, editor behaved strangely
Summary: java.lang.NullPointerException, editor behaved strangely
Status: RESOLVED DUPLICATE of bug 122615
Alias: None
Product: ruby
Classification: Unclassified
Component: Editing (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Torbjorn Norbye
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-25 18:11 UTC by jamespb
Modified: 2007-12-07 16:39 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
log file (87.75 KB, text/plain)
2007-11-25 18:11 UTC, jamespb
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jamespb 2007-11-25 18:11:13 UTC
Started to edit a file, and the editor started to behave strangely.  Arrow keys just beeped, text wasn't deleted when I
hit delete.  Got the flashing do-not-enter icon in the bottom-right corner, and got a java.lang.NullPointerException in
the log.

I'll include the log.
Comment 1 jamespb 2007-11-25 18:11:52 UTC
Created attachment 53455 [details]
log file
Comment 2 jamespb 2007-11-25 18:13:15 UTC
build 5469

Product Version: NetBeans Ruby IDE 20071124202613
Java: 1.6.0_01; Java HotSpot(TM) Client VM 1.6.0_01-b06
System: Windows Vista version 6.0 running on x86; Cp1252; en_US (nbrubyide)
Userdir: C:\Users\James\AppData\Roaming\.nbrubyide\dev
Comment 3 Torbjorn Norbye 2007-11-26 01:25:46 UTC
If this is a download from hudson on deadlock.netbeans.org then the build timestamp shows that this is a 6.1 build, not
6.0. I've seen some similar lexing issues myself in the last week; I think it's a duplicate of 122615. I'll investigate
in detail tomorrow.
Comment 4 jamespb 2007-11-26 01:51:24 UTC
Yes, this is a hudson build - I didn't realize those had changed over to 6.1.
Comment 5 Torbjorn Norbye 2007-11-27 22:30:15 UTC
This is a duplicate of issue 122615 (which was fixed today)

*** This issue has been marked as a duplicate of 122615 ***