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 90231 - Constant error popping up - java.lang.IndexOutOfBoundsException - heavy cpu usage
Summary: Constant error popping up - java.lang.IndexOutOfBoundsException - heavy cpu u...
Status: RESOLVED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 5.x
Hardware: All Linux
: P2 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-29 00:02 UTC by takisd
Modified: 2008-02-25 16:17 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
message log (16.94 KB, text/plain)
2006-11-29 00:11 UTC, takisd
Details

Note You need to log in before you can comment on or make changes to this bug.
Description takisd 2006-11-29 00:02:52 UTC
Hi

the error icon is popping up every few seconds or so. the error message is
actually not visible from it using the show detail button - dialog dumps. 

looking at the log file it was 120MB and growing (hence no attachment - sorry)
with the exception pasted at the end of this message shown over and over again
(don't mean to paste 'large amounts of text' but log file way too big).

also, cpu usage stays constant at between 60-80% - which on a laptop running on
battery is a disaster! (using top on linux - netbeans IS the culprit).

all i'm doing is writing a simple jsp webapp - nothing special.

thanks

Takis

----
log file excerpt:
----

*********** Exception occurred ************ at 10:52 AM on Nov 29, 2006
java.lang.IndexOutOfBoundsException: 526
        at org.netbeans.modules.classfile.ConstantPool.get(ConstantPool.java:90)
       at
org.netbeans.modules.classfile.ConstantPool.getClass(ConstantPool.java:102)
        at
org.netbeans.modules.classfile.ClassFile.loadClassHeader(ClassFile.java:191)
        at org.netbeans.modules.classfile.ClassFile.load(ClassFile.java:160)
        at org.netbeans.modules.classfile.ClassFile.<init>(ClassFile.java:118)
        at
org.netbeans.modules.javacore.scanning.ClassUpdater.getClassFile(ClassUpdater.java:235)
        at
org.netbeans.modules.javacore.scanning.ClassUpdater.updateResources(ClassUpdater.java:124)
        at
org.netbeans.modules.javacore.scanning.ClassUpdater.updateResources(ClassUpdater.java:98)
        at
org.netbeans.modules.javacore.scanning.FileScanner.scanPackage(FileScanner.java:292)
        at
org.netbeans.modules.javacore.scanning.FileScanner.scanPackage(FileScanner.java:249)
        at
org.netbeans.modules.javacore.scanning.FileScanner.scanPackage(FileScanner.java:249)
        at
org.netbeans.modules.javacore.scanning.FileScanner.scan(FileScanner.java:177)
[catch] at org.netbeans.modules.javacore.JMManager.scanFiles(JMManager.java:1183)
        at
org.netbeans.modules.javacore.JMManager.resolveCPRoot(JMManager.java:1097)
        at
org.netbeans.modules.javacore.JMManager.resolveCodebases(JMManager.java:871)
        at org.netbeans.modules.javacore.JMManager$2.run(JMManager.java:821)
        at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:499)
       at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:932)
*********** Exception occurred ************ at 10:52 AM on Nov 29, 2006
java.lang.IndexOutOfBoundsException: 526
        at org.netbeans.modules.classfile.ConstantPool.get(ConstantPool.java:90)
       at
org.netbeans.modules.classfile.ConstantPool.getClass(ConstantPool.java:102)
        at
org.netbeans.modules.classfile.ClassFile.loadClassHeader(ClassFile.java:191)
        at org.netbeans.modules.classfile.ClassFile.load(ClassFile.java:160)
        at org.netbeans.modules.classfile.ClassFile.<init>(ClassFile.java:118)
        at
org.netbeans.modules.javacore.scanning.ClassUpdater.getClassFile(ClassUpdater.java:235)
        at
org.netbeans.modules.javacore.scanning.ClassUpdater.updateResources(ClassUpdater.java:124)
        at
org.netbeans.modules.javacore.scanning.ClassUpdater.updateResources(ClassUpdater.java:98)
        at
org.netbeans.modules.javacore.scanning.FileScanner.scanPackage(FileScanner.java:292)
        at
org.netbeans.modules.javacore.scanning.FileScanner.scanPackage(FileScanner.java:249)
        at
org.netbeans.modules.javacore.scanning.FileScanner.scanPackage(FileScanner.java:249)
        at
org.netbeans.modules.javacore.scanning.FileScanner.scan(FileScanner.java:177)
[catch] at org.netbeans.modules.javacore.JMManager.scanFiles(JMManager.java:1183)
        at
org.netbeans.modules.javacore.JMManager.resolveCPRoot(JMManager.java:1097)
        at
org.netbeans.modules.javacore.JMManager.resolveCodebases(JMManager.java:871)
        at org.netbeans.modules.javacore.JMManager$2.run(JMManager.java:821)
        at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:499)
       at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:932)
Comment 1 takisd 2006-11-29 00:10:37 UTC
cleared log and restarted. 

messages.log attached with ide version/module info etc.

thanks

Takis
Comment 2 takisd 2006-11-29 00:11:31 UTC
Created attachment 36340 [details]
message log
Comment 3 Jiri Kovalsky 2006-12-05 10:59:41 UTC
Looks like a problem in our Java infrastructure. Can you guys please look at the
stack trace and evaluate the issue?
Does it help if you launch NetBeans with an empty userdir and open the project?
netbeans -userdir ../abcd [Enter]
Comment 4 takisd 2006-12-10 12:18:21 UTC
Hi

i tried launching netbeans with no projects open at all. i then opened up my
projects individually. i noticed that it was only the projects with versioning
attached that kicked off the problem. 

i recently switched from cvs repos to subversion. in the process some binary
files didn't convert very well to subversion and had to be removed/recreated. it
appears that some jars referenced from the 'problem' projects were corrupted.
netbeans must of been trying to 'read' them and was constantly dumping. 

ok so perhaps not a netbeans issues as such - which is good. however, even with
corrupt and unreadable jars, it did exhibit some strange behaviour - perhaps it
should have just reported the problem and stopped scanning the problem jars -
the corrupt jar was never reported in fact, just the stack i previously posted.

anyway, with new jars the issue isn't popping up anymore. so all good.

thanks
Takis



Comment 5 Quality Engineering 2007-09-20 12:49:52 UTC
Reorganization of java component
Comment 6 darkgar 2007-09-27 18:55:55 UTC
I have the same as well with the same error output. One odd way I found to fix it was to log into my collaboration
account in NetBeans and close the application with the offending. Then I would re-launch NetBeans and the problem would
be fixed.  

It worked everytime I did this, not sure if it will help you though but its worth a try.

The error for me turned disables refactoring and messes up template creation (causing NB not to set the variable names
macro in the template) which is annoying.

Does the Collab session login re-set the app internally?  Or could the error related to something else like Collaboration?  

(I am using NB 5.5.1, and yes I do do SVN and CVS libraries for projects like jME and LWGL)
Comment 7 Jan Becicka 2008-02-25 16:17:55 UTC
This issue is not valid in current builds any more. Java support was completely
redesigned in 6.0 time frame. Please use NetBeans 6.0 and later.