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 70946 - IndexOutOfBoundsException after applying a class name filter on memory live results
Summary: IndexOutOfBoundsException after applying a class name filter on memory live r...
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: PC All
: P2 blocker (vote)
Assignee: Jiri Sedlacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-03 14:13 UTC by ehucka
Modified: 2007-02-20 18:08 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 ehucka 2006-01-03 14:13:39 UTC 
Profiler 060103, jdk1.5.0_05, Object liveness and GC with stacktraces profiling task

java.lang.IndexOutOfBoundsException: Index: 110, Size: 3
        at java.util.ArrayList.RangeCheck(ArrayList.java:547)
        at java.util.ArrayList.get(ArrayList.java:322)
        at
com.sun.tools.profiler.ui.memory.LivenessResultsPanel$2.getValueAt(LivenessResultsPanel.java:318)
        at
com.sun.tools.profiler.ui.components.ExtendedTableModel.getValueAt(ExtendedTableModel.java:113)
        at javax.swing.JTable.getValueAt(JTable.java:1852)
        at
com.sun.tools.profiler.ui.memory.LiveLivenessResultsPanel.updateLiveResults(LiveLivenessResultsPanel.java:281)
        at
org.netbeans.modules.profiler.LiveResultsWindow$5$1.run(LiveResultsWindow.java:402)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)

Steps to reproduce:
1. start memory profiling of an application
2. open live results window, find 'your' class and select it
3. specify class name filter which filter out your class'es name

The exception is thrown and results are not autoupdated after.
Comment 1 iformanek 2006-01-03 17:33:48 UTC 
Jirko, please evaluate
Comment 2 Jiri Sedlacek 2006-01-03 23:25:37 UTC 
Caused by incorrect selection after applying results filter (happens for both 
CPU & Memory results, but only for Memory exception is thrown). Adjusting 
priority.
Comment 3 Jiri Sedlacek 2006-01-04 12:10:05 UTC 
Fixed for M12.
Comment 4 ehucka 2006-01-17 11:07:30 UTC 
verified
Comment 5 Alexander Kouznetsov 2007-02-20 10:15:50 UTC 
Closing old issues
Comment 6 Alexander Kouznetsov 2007-02-20 18:08:21 UTC 
Reverting to original Target Milestone value changed by mistake. Sorry for
inconvenience.