Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mat-dev] Eclipse

Hello,

Thanks for the answer, although my english is not very well, with your information I have done some changes:

1º) I have put in the VM arguments (Run Configurations -> VM Arguments):  -XX:+HeapDumpOnOutOfMemoryError

2º) Then, I run the code and when the execution has completed, I have seen that has generated it four files: 
      *java_pid2664.hprof
      *java_pid2664.temp.outbound.index
      *java_pid2664.threads
      *hs_err_pid2664.log  --> This I enclose it in the mail

3º) So as I have generated the file hprof, I have tried to open it with Memory Analyzer ( Open Heap Dump) but there is an error, 
I enclose too the screenshot of the error.

Is it possible that the error can be of the Virtual Machine ? 

Thanks so much again for the help,
Regards,
Esteban.



From: krum.tsvetkov@xxxxxxx
To: mat-dev@xxxxxxxxxxx
Date: Mon, 11 Apr 2011 08:38:07 +0200
Subject: Re: [mat-dev] Eclipse

Hello Esteban,

 

MAT works with heap dumps, so the first thing you’ll need is to get a heap dump. Looking at your example, it will be easy to let the VM write one when an OutOfMemoryError occurs. See “Getting a heap dump” [1] for more details.

Then switch to the “Memory analysis” perspective and open the generated heap dump file.

Running the leak suspect report [2] could be a starting point in the analysis.

 

In your case the tool should point to the main thread and a huge Object[]. If you use a 1.6 JDK you would also be able to see the stacktrace.

 

Additional info you can find in the Memory Analyzer help pages. Just go in your Eclipse to “Help” -> “Help Contents” and find Memory Analyzer there.

 

If you need some further help, let us know.

 

Regards,

Krum

 

[1] http://wiki.eclipse.org/index.php/MemoryAnalyzer#Getting_a_Heap_Dump

[2] http://memoryanalyzer.blogspot.com/2008/05/automated-heap-dump-analysis-finding.html

 

Krum Tsvetkov
SAP AG
www.sap.com
http://www.sap.com/company/legal/impressum.epx

 


From: mat-dev-bounces@xxxxxxxxxxx [mailto:mat-dev-bounces@xxxxxxxxxxx] On Behalf Of Esteban Alvarez
Sent: Sonntag, 10. April 2011 21:12
To: mat-dev@xxxxxxxxxxx
Subject: [mat-dev] Eclipse
Importance: High

 

Hello,

 

This weekend I have started to use the tool of Memory Analyzer in Eclipse Classic 3.6.2, but I am having many problems with the execute.

 

1º) For start I have installed the tool of Memory Analyzer (Help -> Install new software...).

2º) Then I created a new Java Project.

3º) In the new Java Project, I have created a Class with this code:

 

 

    import java.util.ArrayList;

            import java.util.List;

             

            public class MemoryAnalicer {

                       private static List<Integer> memoryLeakArea=new ArrayList<Integer>();

                       public static void main(String [] args){

                                   int iteration=0;

                                   while(true){

                                              Integer increaseNumber=new Integer(iteration);

                                              memoryLeakArea.add(increaseNumber);

                                              iteration++;

                                              System.out.println(iteration);

                                   }

                       }          

            }

           

4º) With this code I want detect the memory leaks that it generate with the execute, I know that with the Memory Analyzer it's possible

      but I don't know how.

 

 

For this reason, I would like it to ask you if you can hep me with the problems that I have with Memory Analyzer.

 

Thanks so much for the answer,

Best regards,

Esteban.


_______________________________________________ mat-dev mailing list mat-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/mat-dev
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (compactingPermGenGen.cpp:361), pid=2664, tid=3532
#  Error: ShouldNotReachHere()
#
# JRE version: 7.0-b66
# Java VM: Java HotSpot(TM) Client VM (16.0-b06 mixed mode, sharing windows-x86 )
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#

---------------  T H R E A D  ---------------

Current thread (0x02b2a800):  VMThread [stack: 0x02ba0000,0x02bf0000] [id=3532]

Stack: [0x02ba0000,0x02bf0000],  sp=0x02befd1c,  free space=13f02befd2ck
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V  [jvm.dll+0x1f3a00]
V  [jvm.dll+0xa2059]
V  [jvm.dll+0x82eb0]
V  [jvm.dll+0xcd9ee]
V  [jvm.dll+0xd2edc]
V  [jvm.dll+0x1f6673]
V  [jvm.dll+0x1f590e]
V  [jvm.dll+0x1f5c5c]
V  [jvm.dll+0x1f6082]
V  [jvm.dll+0x17f09c]
C  [msvcr71.dll+0x9565]
C  [kernel32.dll+0xb729]

VM_Operation (0x0092f784): HeapDumper, mode: safepoint, requested by thread 0x00856800


---------------  P R O C E S S  ---------------

Java Threads: ( => current thread )
  0x02b3e000 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=128, stack(0x02d80000,0x02dd0000)]
  0x02b37c00 JavaThread "CompilerThread0" daemon [_thread_blocked, id=724, stack(0x02d30000,0x02d80000)]
  0x02b36400 JavaThread "Attach Listener" daemon [_thread_blocked, id=3864, stack(0x02ce0000,0x02d30000)]
  0x02b35000 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=2960, stack(0x02c90000,0x02ce0000)]
  0x02b30800 JavaThread "Finalizer" daemon [_thread_blocked, id=3908, stack(0x02c40000,0x02c90000)]
  0x02b2bc00 JavaThread "Reference Handler" daemon [_thread_blocked, id=700, stack(0x02bf0000,0x02c40000)]
  0x00856800 JavaThread "main" [_thread_blocked, id=3080, stack(0x008e0000,0x00930000)]

Other Threads:
=>0x02b2a800 VMThread [stack: 0x02ba0000,0x02bf0000] [id=3532]
  0x02b3fc00 WatcherThread [stack: 0x02dd0000,0x02e20000] [id=3576]

VM state:at safepoint (normal execution)

VM Mutex/Monitor currently owned by a thread:  ([mutex/lock_event])
[0x008557a8] Threads_lock - owner thread: 0x02b2a800
[0x00855bb8] Heap_lock - owner thread: 0x00856800

Heap
 def new generation   total 4544K, used 4543K [0x229f0000, 0x22ed0000, 0x22ed0000)
  eden space 4096K, 100% used [0x229f0000, 0x22df0000, 0x22df0000)
  from space 448K,  99% used [0x22e60000, 0x22ecffd8, 0x22ed0000)
  to   space 448K,   0% used [0x22df0000, 0x22df0000, 0x22e60000)
 tenured generation   total 60544K, used 60543K [0x22ed0000, 0x269f0000, 0x269f0000)
   the space 60544K,  99% used [0x22ed0000, 0x269efff8, 0x269f0000, 0x269f0000)
 compacting perm gen  total 12288K, used 53K [0x269f0000, 0x275f0000, 0x2a9f0000)
   the space 12288K,   0% used [0x269f0000, 0x269fd758, 0x269fd800, 0x275f0000)
    ro space 8192K,  63% used [0x2a9f0000, 0x2af0a160, 0x2af0a200, 0x2b1f0000)
    rw space 12288K,  53% used [0x2b1f0000, 0x2b84e488, 0x2b84e600, 0x2bdf0000)

Dynamic libraries:
0x00400000 - 0x00423000 	C:\Archivos de programa\Java\jre7\bin\javaw.exe
0x7c910000 - 0x7c9c8000 	C:\WINDOWS\system32\ntdll.dll
0x7c800000 - 0x7c903000 	C:\WINDOWS\system32\kernel32.dll
0x77da0000 - 0x77e4c000 	C:\WINDOWS\system32\ADVAPI32.dll
0x77e50000 - 0x77ee3000 	C:\WINDOWS\system32\RPCRT4.dll
0x77fc0000 - 0x77fd1000 	C:\WINDOWS\system32\Secur32.dll
0x7e390000 - 0x7e421000 	C:\WINDOWS\system32\USER32.dll
0x77ef0000 - 0x77f39000 	C:\WINDOWS\system32\GDI32.dll
0x773a0000 - 0x774a3000 	C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.6028_x-ww_61e65202\COMCTL32.dll
0x77be0000 - 0x77c38000 	C:\WINDOWS\system32\msvcrt.dll
0x77f40000 - 0x77fb6000 	C:\WINDOWS\system32\SHLWAPI.dll
0x76340000 - 0x7635d000 	C:\WINDOWS\system32\IMM32.DLL
0x7c340000 - 0x7c396000 	C:\Archivos de programa\Java\jre7\bin\msvcr71.dll
0x6d790000 - 0x6da25000 	C:\Archivos de programa\Java\jre7\bin\client\jvm.dll
0x76b00000 - 0x76b2e000 	C:\WINDOWS\system32\WINMM.dll
0x6d740000 - 0x6d74b000 	C:\Archivos de programa\Java\jre7\bin\verify.dll
0x6d290000 - 0x6d2af000 	C:\Archivos de programa\Java\jre7\bin\java.dll
0x6d210000 - 0x6d218000 	C:\Archivos de programa\Java\jre7\bin\hpi.dll
0x76bb0000 - 0x76bbb000 	C:\WINDOWS\system32\PSAPI.DLL
0x6d780000 - 0x6d790000 	C:\Archivos de programa\Java\jre7\bin\zip.dll

VM Arguments:
jvm_args: -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=Cp1252 
java_command: MemoryAnalicer
Launcher Type: SUN_STANDARD

Environment Variables:
CLASSPATH=.;C:\Archivos de programa\Java\jre6\lib\ext\QTJava.zip
PATH=C:/Archivos de programa/Java/jre7/bin/client;C:/Archivos de programa/Java/jre7/bin;C:/Archivos de programa/Java/jre7/lib/i386;C:\Archivos de programa\Mozilla Firefox;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Archivos de programa\QuickTime\QTSystem\;C:\ARCHIV~1\Tcl\bin;C:\Archivos de programa\Java\jre6\bin;C:\eclipse;
USERNAME=ASUS
OS=Windows_NT
PROCESSOR_IDENTIFIER=x86 Family 6 Model 28 Stepping 2, GenuineIntel



---------------  S Y S T E M  ---------------

OS: Windows XP Build 2600 Service Pack 3

CPU:total 2 (1 cores per cpu, 2 threads per core) family 6 model 28 stepping 2, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, ht

Memory: 4k page, physical 2088108k(1080736k free), swap 3490832k(2640776k free)

vm_info: Java HotSpot(TM) Client VM (16.0-b06) for windows-x86 JRE (1.7.0-ea-b66), built on Jul 24 2009 03:23:51 by "java_re" with MS VC++ 7.1 (VS2003)

time: Wed Mar 30 11:30:36 2011
elapsed time: 245 seconds

Attachment: error hprof.bmp
Description: Windows bitmap


Back to the top