Hi, LeO, I am not sure about whether the Memory-Execution problem you encountered is related with Profiler crash. However, if you just want to get profiling data for your objects, maybe you can try with the filter option before profiling. You can find about filter usage in TPTP help documents. Another suggestion about the problem: please try with some other applications with Memory profiling to make sure whether the problem happens just on a special application or it is a general problem.
Thanks, -------------------------------------------------- Chengrui Deng China Runtime Technologies Lab, SSG/SSD/MRTC, Intel -------------------------------------------------- -----Original Message----- From: tptp-tracing-profiling-tools-dev-boun...@eclipse.org [mailto:tptp-tracing-profiling-tools-dev-boun...@eclipse.org] On Behalf Of leo4...@turboprinz.de Sent: 2009年6月8日 16:53 To: tptp-tracing-profiling-tools-dev@eclipse.org Subject: [tptp-tracing-profiling-tools-dev] Profiling crashh Hi, I am not pretty sure, if I am posting on the proper Mailing List. If not, please give me a hint, where to post in a more appropriate way. I have downloaded TPTP-4.6.0-200906041936 and thought, it might solve some of my problems I experienced with 3.4. Unfortunately not. (Java 1.6.013 on WinXP, 2GB, 2x1,66GHz) The current problem: I can launch my application for profiling, either as Memory-Execution (ME) or Execution Time Analysis (ETA). With the ETA I have no problems at all, while I have serious problems with ME. Since I wanna detect Mem-Leaks I am interested in ME and not the other possibilities. What happens: During the launch process the profiler seems to crash. I cannot click on my application and all I can do is to terminate. At the start up there are plenty of DB-accesses as well as remote server accesses. Splitted into several threads. I can even click on the Pause-button during start-up but the problem remains. Sometimes (1 out of 30-40) the app could be launched. When I stop the app, I can see as well some data are collected. Interesting part is to see, the CPU-consumption goes up to 100% for some time and then remains to 0%. From this I conclude, the Profiler crash. Since the ETA works while the ME not, I do not see it as a generic setup problem. I have Object-data and would assume they are counted properly. Question: What can I do to get profiling data for my objects? (Without rewritting my code to work with TPTP) I could also raise a Bug, but frankly said, I have no idea, what to post there resp. what kind of symptoms are relevant, what kind of traces are required, etc.... Thx if somebody could help :) LeO -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 _______________________________________________ tptp-tracing-profiling-tools-dev mailing list tptp-tracing-profiling-tools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-dev
_______________________________________________ tptp-tracing-profiling-tools-dev mailing list tptp-tracing-profiling-tools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-dev
