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 78787 - Profiler crashes on Analyze Performance
Summary: Profiler crashes on Analyze Performance
Status: RESOLVED FIXED
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-06-21 16:12 UTC by kitfox
Modified: 2006-07-27 10:54 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
log (64.21 KB, text/plain)
2006-06-21 16:13 UTC, kitfox
Details
log (17.05 KB, text/plain)
2006-06-21 20:18 UTC, kitfox
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kitfox 2006-06-21 16:12:02 UTC
I've recently upgraded to Netbeans 5.5 beta with Java 1.6.88b.  While I was
previously able to run the profiler in Analyze Performance mode, I am now
getting errors saying that it cannot connect.

I'm running the profiler as part of a freeform project.  Below is my profiling
and script:

    <target name="profile" depends="init,compile" description="Profile Project">
        <fail unless="netbeans.home">This target can only run inside the
NetBeans IDE.</fail>
        <echo message="${project.profile.mainClass}"/>
        <nbprofiledirect>
            <classpath>
                <pathelement path="."/>
                <pathelement path="${classes.dir}"/>
                <path refid="path.classpath"/>
            </classpath>
        </nbprofiledirect>

        <java classname="${project.profile.mainClass}"
classpath="${classes.dir}" fork="true">
            <jvmarg value="${profiler.info.jvmargs.agent}"/>
            <jvmarg value="-ea"/>
            <jvmarg value="-Xmx256M"/>
            <jvmarg value="-Djogl.verbose"/>
            <classpath>
                <pathelement location=""/>
                <path refid="path.classpath"/>
            </classpath>
        </java>
    </target>
Comment 1 kitfox 2006-06-21 16:13:35 UTC
Created attachment 31281 [details]
log
Comment 2 Jiri Sedlacek 2006-06-21 16:18:06 UTC
Seems like a known issue with newest 1.6 builds on Windows - profiling fails on 
builds 86 and newer on Windows when instrumenting core Java classes.

Please try one of following and let us know:

 1/ Use 1.6 build before 86
 2/ Use 1.6 build 86 and newer with -Xshare:off option
 3/ Use "Exclude Core Java Classes" instrumentation filter when using 1.6 build 
86 and newer
Comment 3 kitfox 2006-06-21 20:16:53 UTC
I tried option 2 below, and while the profiler did start, it crashed as soon as
I put any load on my program.  I'm attaching the dump.
Comment 4 kitfox 2006-06-21 20:18:10 UTC
Created attachment 31287 [details]
log
Comment 5 Tomas Hurka 2006-06-21 20:40:36 UTC
The JVM crash does not seem to be caused by profiling. Can you please try to downgrade build 85 and see 
what happen. Thanks.
 
Comment 6 kitfox 2006-06-22 05:03:23 UTC
Okay.  What release is a bug fix for this expected in?
Comment 7 Tomas Hurka 2006-06-22 06:58:25 UTC
I don't know.
Comment 8 Tomas Hurka 2006-07-27 10:54:56 UTC
The problem is fixed in Mustang build 92.
Closing as fixed - please use Mustang build 92 or newer. You can download it here 
https://mustang.dev.java.net/