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 121710 - Empty live results and snapshots on memory profiling
Summary: Empty live results and snapshots on memory profiling
Status: RESOLVED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-12 10:55 UTC by Alexander Kouznetsov
Modified: 2011-10-04 11:10 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Video (3.33 MB, application/octet-stream)
2007-11-12 10:56 UTC, Alexander Kouznetsov 		Details
Messages.log (277.23 KB, text/plain)
2007-11-12 10:59 UTC, Alexander Kouznetsov 		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 Alexander Kouznetsov 2007-11-12 10:55:42 UTC 
Product Version: NetBeans IDE 6.0 RC1 (Build 200711120000)
Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05
System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb)

This issue is random but not it is captured. See attached video.
Comment 1 Alexander Kouznetsov 2007-11-12 10:56:59 UTC 
Created attachment 52870 [details]
Video
Comment 2 Alexander Kouznetsov 2007-11-12 10:59:13 UTC 
Created attachment 52871 [details]
Messages.log
Comment 3 Alexander Kouznetsov 2007-11-12 13:02:05 UTC 
I also got the following exception during attempts to reproduce this issue:
java.lang.ArrayIndexOutOfBoundsException: 3
	at org.netbeans.lib.profiler.results.memory.MemoryDataFrameProcessor.doProcessDataFrame(MemoryDataFrameProcessor.java:90)
	at org.netbeans.lib.profiler.results.AbstractDataFrameProcessor.processDataFrame(AbstractDataFrameProcessor.java:85)
	at org.netbeans.lib.profiler.results.ProfilingResultsDispatcher$2.run(ProfilingResultsDispatcher.java:160)
	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)

Is it related problem or should I file it separately?
Comment 4 Alexander Kouznetsov 2007-11-15 17:31:28 UTC 
Filed separate issue 122043 for AIOOBE
Comment 5 J Bachorik 2008-03-29 11:41:41 UTC 
changing milestone
Comment 6 J Bachorik 2011-10-04 11:10:40 UTC 
Works in the 7.1 dev build as of Oct 4, 2011