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 104572 - Memory profilers of large projects wreak havok
Summary: Memory profilers of large projects wreak havok
Status: VERIFIED DUPLICATE of bug 104573
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-23 05:51 UTC by apb
Modified: 2007-09-10 10:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
messages.log (116.34 KB, text/plain)
2007-06-08 18:46 UTC, patrick133t 		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 apb 2007-05-23 05:53:23 UTC 
I have a very large project and every single time I try to run a memory profile
on it, the profiler crashes in netbeans when it instruments the 3,435th class.
This happen under Suse 10.1 64 bit and under Windows XP 64 bit with both Java
1.6.0 and 1.6.0_1 (I haven't tried it on any other platforms).

Here is the error:

java.lang.ArrayIndexOutOfBoundsException
	at java.lang.System.arraycopy(Native Method)
	at
com.sun.tools.profiler.instrumentation.SingleMethodScaner.initBytecodesArray(SingleMethodScaner.java:147)
	at
com.sun.tools.profiler.instrumentation.SingleMethodScaner.setClassAndMethod(SingleMethodScaner.java:42)
	at
com.sun.tools.profiler.instrumentation.MemoryProfMethodInstrumentor.hasNewOpcodes(MemoryProfMethodInstrumentor.java:125)
	at
com.sun.tools.profiler.instrumentation.ObjLivenessMethodInstrumentor.methodNeedsInstrumentation(ObjLivenessMethodInstrumentor.java:42)
	at
com.sun.tools.profiler.instrumentation.MemoryProfMethodInstrumentor.findAndMarkMethodsToInstrumentInClass(MemoryProfMethodInstrumentor.java:107)
	at
com.sun.tools.profiler.instrumentation.MemoryProfMethodInstrumentor.getMethodsToInstrumentUponClassLoad(MemoryProfMethodInstrumentor.java:71)
	at
com.sun.tools.profiler.instrumentation.Instrumentor.createFollowUpInstrumentMethodGroupResponseForMemoryProfiling(Instrumentor.java:463)
	at
com.sun.tools.profiler.instrumentation.Instrumentor.createFollowUpInstrumentMethodGroupResponse(Instrumentor.java:157)
	at
com.sun.tools.profiler.ProfilerClient.instrumentMethodGroupFollowUp(ProfilerClient.java:901)
	at com.sun.tools.profiler.ProfilerClient.access$2900(ProfilerClient.java:46)
[catch] at
com.sun.tools.profiler.ProfilerClient$SeparateCmdExecutionThread.run(ProfilerClient.java:1603)
Comment 1 apb 2007-05-23 05:59:49 UTC 

*** This issue has been marked as a duplicate of 104573 ***
Comment 2 patrick133t 2007-06-08 18:46:09 UTC 
Created attachment 43451 [details]
messages.log
Comment 3 Alexander Kouznetsov 2007-09-10 10:26:36 UTC 
Verified duplicate