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.
Sometimes when I am profiling my application, I got the following error: java.lang.ArrayIndexOutOfBoundsException: 5000 at com.sun.tools.profiler.server.ProfilerRuntimeCPU.writeTimeStampedEvent(ProfilerRuntimeCPU.java:68) at com.sun.tools.profiler.server.ProfilerRuntimeCPUFullInstr.methodEntry(ProfilerRuntimeCPUFullInstr.java:92) at antlr.InputBuffer.LA(InputBuffer.java:86) at antlr.CharScanner.LA(CharScanner.java:169) at quipoz.transform.language.C.MicrosoftC.MSCLexer.mIDENTIFIER(MSCLexer.java:523) at quipoz.transform.language.C.MicrosoftC.MSCLexer.nextToken(MSCLexer.java:188) at antlr.TokenStreamBasicFilter.nextToken(TokenStreamBasicFilter.java:39) at antlr.TokenStreamSelector.nextToken(TokenStreamSelector.java:68) at antlr.TokenBuffer.fill(TokenBuffer.java:69) at antlr.TokenBuffer.LA(TokenBuffer.java:81) at antlr.LLkParser.LA(LLkParser.java:52) at quipoz.transform.language.C.MicrosoftC.MSCParser.structUnionType(MSCParser.java:7283) at quipoz.transform.language.C.MicrosoftC.MSCParser.type(MSCParser.java:6718) at quipoz.transform.language.C.MicrosoftC.MSCParser.declarationSpecifiers(MSCParser.java:4958) at quipoz.transform.language.C.MicrosoftC.MSCParser.variableDeclarationTest(MSCParser.java:2376) at quipoz.transform.language.C.MicrosoftC.MSCParser.logicProcessing(MSCParser.java:2318) at quipoz.transform.language.C.MicrosoftC.CBAProgramParserC.parse(CBAProgramParserC.java:105) at quipoz.transform.process.FileLoader.processFile(FileLoader.java:101) at quipoz.transform.process.FileLoader$1.run(FileLoader.java:85) at edu.emory.mathcs.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:655) at edu.emory.mathcs.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676) at java.lang.Thread.run(Thread.java:536)
Fixed the possible cause for this issue, the code will become available in Milestone 3 release due in the beginning of November 2004. Without a real use case from the user, however, it's difficult to make sure the real root cause for the problem is identified/fixed. Can make the updated .nbm file, effectively a preview of M3 release, available on demand to the user for testing.
old issue, closed