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 185341 - sun.org.mozilla.javascript.internal.EvaluatorException: illegal character (<Unknown Source>#1)
Summary: sun.org.mozilla.javascript.internal.EvaluatorException: illegal character (<U...
Status: RESOLVED WORKSFORME
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: J Bachorik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-03 09:01 UTC by Daniel Prusa
Modified: 2010-10-06 15:44 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 168998

Attachments
stacktrace (2.14 KB, text/plain)
2010-05-03 09:01 UTC, Daniel Prusa 		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 Daniel Prusa 2010-05-03 09:01:10 UTC 
Build: NetBeans IDE Dev (Build 100429-e86f264d4651)
VM: Java HotSpot(TM) Client VM, 14.0-b16, Java(TM) SE Runtime Environment, 1.6.0_14-b08
OS: Windows Vista

User Comments:
dprusa: While exiting IDE (there was one processes running, not sure if this is important).




Stacktrace: 
sun.org.mozilla.javascript.internal.EvaluatorException: illegal character (<Unknown Source>#1)
   at sun.org.mozilla.javascript.internal.DefaultErrorReporter.runtimeError(DefaultErrorReporter.java:84)
   at sun.org.mozilla.javascript.internal.DefaultErrorReporter.error(DefaultErrorReporter.java:71)
   at sun.org.mozilla.javascript.internal.Parser.addError(Parser.java:111)
   at sun.org.mozilla.javascript.internal.TokenStream.getToken(TokenStream.java:796)
   at sun.org.mozilla.javascript.internal.Parser.peekToken(Parser.java:129)
   at sun.org.mozilla.javascript.internal.Parser.parse(Parser.java:323)
Comment 1 Daniel Prusa 2010-05-03 09:01:17 UTC 
Created attachment 98350 [details]
stacktrace
Comment 2 J Bachorik 2010-10-06 15:44:12 UTC 
Are you able to reproduce this problem? It seems that the only way to get this exception would be to get a corrupted data from a certain JS file.