Fully featured low overhead profiler for Java EE and Java SE platforms.
Ultimate profiling and monitoring solution for Gradle, Maven, Ant, JUnit and TestNG.
Easy to use performance and memory profiler for .NET framework.

500 elements limit for arrays in "Object explorer"

Moderators: Vladimir Kondratyev, Anton Katilin

500 elements limit for arrays in "Object explorer"

Postby wantosz » Tue Sep 04, 2007 8:38 pm

Let say I have an array of size 600. I would like to be able to inspect, for example, the last element. The "Object explorer" lists first 500 only and shows "and more..." below, but there appears no way for me to either advance to next 500 or view element at specific index. Am I missing something?

(PS. I am viewing an HPROF dump)
wantosz
 
Posts: 1
Joined: Tue Sep 04, 2007 8:29 pm

Postby Anton Katilin (YourKit) » Tue Sep 04, 2007 8:46 pm

Hello,

This number is hardcoded.

We'll add ability to advance to next 500 or similar means to browse more elements in future version.

Could you please provide more detail on why you need to manually browse content of such big array. I hope I'll be able to suggest suitable workaround and/or an alternate approach.

Best regards,
Anton
Anton Katilin (YourKit)
 
Posts: 157
Joined: Wed Aug 15, 2007 9:09 pm

Postby zenkar » Thu Mar 20, 2008 10:09 pm

I have same issue.

I have two lists of instances for a given class in two snapshots. The lists are about 4800 items long. They differ in ONE instance. I need to know which one it is and all I get is "and more..." at the end of the list.
zenkar
 
Posts: 1
Joined: Thu Mar 20, 2008 10:06 pm

Postby Anton Katilin » Fri Mar 21, 2008 10:28 am

You can try "Memory | Retained Objects..." (Shift+F4) for each of the lists, and then analyze content of a new tab which will open.
Anton Katilin
 
Posts: 5574
Joined: Wed Aug 11, 2004 8:37 am

Re:

Postby Yannis » Wed Nov 30, 2016 10:48 am

Anton Katilin (YourKit) wrote:We'll add ability to advance to next 500 or similar means to browse more elements in future version.

Hi !

Any news on this since 2007 ? ;-)

We are currently trying to address the memory retention issue that using File.deleteOnExit() causes (cf. https://bugs.openjdk.java.net/browse/JDK-4872014) and we would like to export all the strings that the LinkedHashSet of java.io.DeleteOnExitHook holds, in order to figure out which file name patterns are the most offending and whether a punctual fix would be enough in the short term.

As of YourKit 2016.02-b43, the "Open collection elements in a new tab" link only shows the 500 first (?) elements, with no way to display more elements, or export them, etc.

How could we do that (or something similar) ?

Thanks in advance for your answer !
Yannis
 
Posts: 15
Joined: Wed Oct 02, 2013 10:07 am

Re: 500 elements limit for arrays in "Object explorer"

Postby Anton Katilin » Wed Nov 30, 2016 5:27 pm

There is no dedicated UI for this purpose yet, sorry.

As a workaround, please specify the property (with even bigger value, if necessary) -Dyjp.max.objects.to.show=100000 in <user home>/.yjp/ui.ini
Anton Katilin
 
Posts: 5574
Joined: Wed Aug 11, 2004 8:37 am

Re: 500 elements limit for arrays in "Object explorer"

Postby Yannis » Mon Dec 05, 2016 2:15 pm

Seems to work like a charm, and a parameter is fine enough : thanks !
Yannis
 
Posts: 15
Joined: Wed Oct 02, 2013 10:07 am


Return to Java Profiler

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 5 guests

cron