|Re: profiling doesn't stop [message #509194 is a reply to message #508978]
||Thu, 21 January 2010 16:00
| Eugene Chan
Registered: July 2009
What TPTP release are you using? Was there any filtering configuration in
your Java profile session? Try the following, shut down Eclipse, kill the
ACServer.exe and any dangling java.exe running on your machine (check Task
Manager), delete or move the existing servicelog file out from the default
directory; then restart Eclipse workbench with a fresh workspace, and start
a fresh profile, configure the filter similar to the following:
myPackageName* * INCLUDE
* * EXCLUDE
where myPackageName is the package prefix of your target Java application.
See if that helps.
Could you also send me the servicelog file if the problem happens again, the
new one created in the default directory.
<firstname.lastname@example.org> wrote in message news:email@example.com...
> This is my first time to use TPTP to profile my java program, and I got
> into some problem.
> Usually my java program can terminate in about 30 seconds. But by
> profiling it, it seems to take much much longer time. I tried to profile
> it for three times, and for all of them it didn't stop after 1 hours. For
> one run I had to manually stop it. For the other two runs, when I came
> back to my computer after a few hours, Eclipse just disappeared, without
> any error message left. Another thing that I found is, even when I pause
> the profiling, Eclipse still uses nearly 100% CPU time.
> I wonder whether there's something wrong and how I can fix it. Thank you
> in advance.
Powered by FUDForum
. Page generated in 0.02294 seconds