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 86703 - ArrayIndexOutOfBoundsException after OutOfMemory error
Summary: ArrayIndexOutOfBoundsException after OutOfMemory error
Status: RESOLVED DUPLICATE of bug 88707
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-06 19:22 UTC by tjquinn
Modified: 2009-04-29 18:46 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
messages.log as instructed in error dialog (74.68 KB, text/plain)
2006-10-06 19:23 UTC, tjquinn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tjquinn 2006-10-06 19:22:29 UTC
I received an index out of range exception from the profiler.  Will attach the log.
Comment 1 tjquinn 2006-10-06 19:23:28 UTC
Created attachment 35001 [details]
messages.log as instructed in error dialog
Comment 2 Jiri Sedlacek 2006-10-06 19:34:32 UTC
I can see that the problem occurred during CPU profiling after
java.lang.OutOfMemoryError: Java heap space. You've modified profiling (changed
instrumentation filter) and the java.lang.ArrayIndexOutOfBoundsException was
thrown. Are you able to reproduce the AIOOB again without the OutOfMemoryError? 

Note that you should set root methods and/or as much restrictive instrumentation
filter as possible to lower profiling overhead and get only the data you are
really interested in (unless you want to profile the server itself, not the
webapp/ejb). This would help you in preventing the OutOfMemoryError.
Comment 3 Tomas Hurka 2006-10-06 19:43:34 UTC
or you can increase -Xmx as stated in the message.log you attached. 
Comment 4 tjquinn 2006-10-06 20:02:05 UTC
Right on two counts.  I was profiling the app server itself looking for
hotspots. I had limited the classes of interest somewhat but, until we know what
we're looking for we have to cast the net widely.

Also, yes I did notice the OOME.  I know it can be difficult to recover
gracefully from those, but would it be possible to either isolate the impact to
the profiling, displaying a message to that effect and essentially shutting down
the profiling module at that point or, if I should always restart NB upon seeing
an OOME then add a warning to that effect in the display of the OOME in the
first place?

- Tim
Comment 5 Jiri Sedlacek 2007-01-03 12:28:42 UTC
Actually the OOME can be thrown from anywhere inside the IDE (not only in 
Profiler) and the Profiler isn't able to detect it and warn the user.

Won't fix in 6.0.
Comment 6 Tomas Hurka 2008-08-21 07:51:14 UTC
Issue #88707 is the same case. 

*** This issue has been marked as a duplicate of 88707 ***
Comment 7 Quality Engineering 2009-04-29 18:46:25 UTC
Integrated into 'main-golden', will be available in build *200904291401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/5f222f24d38f
User: Jaroslav Bachorik <yardus@netbeans.org>
Log: #86703 - resetting the client data in case of OOME