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 148775 - AIOBE during full instrumentation withtin WinXP wihtin VMWare
Summary: AIOBE during full instrumentation withtin WinXP wihtin VMWare
Status: RESOLVED INVALID
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-30 18:00 UTC by pbouche
Modified: 2009-09-18 11:55 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Messages log (64.26 KB, text/plain)
2008-09-30 18:02 UTC, pbouche 		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 pbouche 2008-09-30 18:00:49 UTC 
The summary pretty much details the problem.

Here is the exception:

java.lang.ArrayIndexOutOfBoundsException: 525187
	at org.netbeans.lib.profiler.results.cpu.CPUDataFrameProcessor.doProcessDataFrame(CPUDataFrameProcessor.java:103)
	at org.netbeans.lib.profiler.results.AbstractDataFrameProcessor.processDataFrame(AbstractDataFrameProcessor.java:85)
	at org.netbeans.lib.profiler.results.ProfilingResultsDispatcher$1.run(ProfilingResultsDispatcher.java:128)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
[catch] at java.lang.Thread.run(Thread.java:619)

The message log is attached.
Comment 1 pbouche 2008-09-30 18:02:33 UTC 
Created attachment 70923 [details]
Messages log
Comment 2 J Bachorik 2008-10-01 08:28:45 UTC 
From the message log it's obvious that there had happened an OOME some time before AIOOBE started to appear. Are you
able to reproduce the problem without incurring the OOME first?
Comment 3 Tomas Hurka 2009-04-08 10:08:03 UTC 
Target milestone cleanup.
Comment 4 Tomas Hurka 2009-04-08 12:52:21 UTC 
Milestone cleanup: future->next
Comment 5 matusdekanek 2009-09-18 11:55:27 UTC 
missing information for a few months -> resolving invalid. 
Reporter: if you reproduce it again and without the OOME, please reopen, thanks in advance.