Thomas Wolf <mailto:tjw...@gmail.com>> wrote:
>> I haven’t used the NB profiler for a year or so, but last time I did
>> (running on an x86 mac in NB 12), it ran fine.
>>
>> Today I tried to profile my standalone JSE application in NB 16 with JDK
>> 17.
Perhaps the same or related to this:
https://github.com/apache/netbeans/issues/4524
Scott
On Thu, Feb 23, 2023 at 1:57 PM Thomas Wolf wrote:
> I haven’t used the NB profiler for a year or so, but last time I did
> (running on an x86 mac in NB 12), it ran fine.
>
> Today I tried t
I haven’t used the NB profiler for a year or so, but last time I did (running
on an x86 mac in NB 12), it ran fine.
Today I tried to profile my standalone JSE application in NB 16 with JDK 17.05
on my ARM-based Mac for the first time and the profiler just sits in a
calibration dialog (see 1st
Hi,
Profiler calibration on Mac M1 Pro failed.
Thanks in advance for any suggestion/fix.
*** Profiler message (Mon Dec 05 21:58:59 CET 2022): Starting target =
application...
/Library/Java/JavaVirtualMachines/zulu-8.jdk/Contents/Home/bin/java =
-agentpath:/Applications/NetBeans/Apache NetBeans
Hi,
Whene I run the profiler on Netbeans 12.5 and 12.6 I am getting the =
following error:
[ERROR] Failed to execute goal =
org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (default-cli) on project =
ae: The parameters 'executable' for goal =
org.codehaus.mojo:exec-maven-plugin:1.2.
021, 08:06 Bradley Willcott,
wrote:
> Hi there,
>
> Should I put this into a bug report?
>
> This showed up when I was trying to profile an application that was
> accessing MySQL server. I was profiling SQL Queries:
>
> Profiler Agent: Waiting for connection on port 5140, timeo
Sorry, I forgot to provide some context:
Netbeans 12.1
Fedora Linux 32
This text appears before the program starts to run, and just after it
has been successfully compiled.
Brad.
Forwarded Message
Subject:Profiler warnings - Illegal reflective access
Date: Sun, 14
Hi there,
Should I put this into a bug report?
This showed up when I was trying to profile an application that was
accessing MySQL server. I was profiling SQL Queries:
Profiler Agent: Waiting for connection on port 5140, timeout 10 seconds
(Protocol version: 18)
Profiler Agent: Established
Hi all,
I am profiling a remote JVM that I have some code running upon. Whilst the
visual view is good I would like to look at some specific events in more
detail. Is the raw data saved off?
Thanks
Chris
CONFIDENTIALITY NOTICE This message and any included attachments are from
Cerner Corpora
Hi Chris,
Do you try to profile Maven or the Java process launched with Maven?
Which Maven plugin do you use to run your app?
On Thu, Dec 6, 2018 at 3:34 PM Luff,Chris
wrote:
> I have just tried to connect the Profiler to a maven build. The build is
> JDK 1.8 on Maven 3.5.4 reactor buil
I have just tried to connect the Profiler to a maven build. The build is JDK
1.8 on Maven 3.5.4 reactor build of 6 modules. When hitting attach the already
running Java process I get a message dialog; Error 0.
Something I am not doing correctly, stupidity or possibly an issue?
Product Version
On Mon, Oct 1, 2018 at 2:32 PM Glenn Holmer wrote:
> +1, we can always use more people in the Profiler tribe.
OK, done.
-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: user
where you'll be able
> to test and try out, for example, the Profiler as part of NetCAT:
>
> https://cwiki.apache.org/confluence/display/NETBEANS/NetCAT+10.0+Participants
+1, we can always use more people in the Profiler tribe.
> On Mon, Oct 1, 2018 at 2:55 PM Peter Hull <mai
#x27;ll be able to
test and try out, for example, the Profiler as part of NetCAT:
https://cwiki.apache.org/confluence/display/NETBEANS/NetCAT+10.0+Participants
Gj
On Mon, Oct 1, 2018 at 2:55 PM Peter Hull wrote:
> I have been trying to the use the NB9.0 profiler on a Java SE project and
>
I have been trying to the use the NB9.0 profiler on a Java SE project and
JDK 11, but I get a JVM crash. Before I put together a bug report, I'd be
very grateful if anyone out there could just quickly let me know if they've
either 1) seen this crash or 2) used the profiler successful
On 07/14/2018 10:49 AM, Glenn Holmer wrote:
> Source level is set to 9, Java platform is JDK10. Running under OpenJDK
> 10. I was also on the profiler tribe for NetCAT. We only tested against
> 8 and 10 since we knew that 9 would be superseded by the time NetBeans
> 9.0 was released
teps:
> Create new java application with main class.
> Add System.out.println("Hello world");
> Change java platform to java9 (properties).
> Change source/binary format to java9 (properties).
> Run profiler, methods, all classes.
Source level is set to 9, Java platform is J
Hi Everyone,
I also have no issues with the profiler (ran through the same steps as
outlined by Alan) on OS X 10.13.5. I was part of the NetCAT for profiler
as well. I am leaning towards a Windows-specific issue perhaps.
Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
https
Hi all..
I was part of the NetCat Profiler tribe and I remember having some problems
in the early phase but nothing later on...
I am using OS X... so maybe something
specific with Windows?
What version of Windows are you using...
@NetCat anyone able to reproduce?
I still have to check the
Well, I’m a little bit surprised by these developments since fixes have
been put in specificslly to enable the Profiler to work with JDK 9 and 10,
by Sven Reimers and Jan Lahoda, so a bit more investigation needs to be
done before drawing any conclusions here.
Gj
On Saturday, July 14, 2018
#x27;s fault - as I understand it, it should not
be possible to crash the JVM like this from Java code (correct me if
I'm wrong!). Alan has reported this to Oracle and I will be interested
to see the response. However, wherever the problem lies, the result is
that NB's profiler doesn't
that some problems in the Profiler area
have already been fixed and so this must be something different.
I hope you understand. We can’t create another whole new build and restart
voting from scratch at this stage, unless we as a community decide that
this is what must be done, delaying the release
Obviously I can't speak for anyone else, but I am using vc3 which I
understand is the latest version (newer than rc1, is that correct?)
Pete
On Sat, 14 Jul 2018 at 08:02 Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:
> Are you using rc1 or the vc3 build?
>
> See blogs.apache.org/ne
Are you using rc1 or the vc3 build?
See blogs.apache.org/netbeans.
Thanks,
Gj
On Saturday, July 14, 2018, Peter Hull wrote:
> On Fri, Jul 13, 2018 at 8:39 PM Glenn Holmer
> wrote:
> >
> > [Sorry if this appears twice, T-bird crashed while sending.]
> I only saw it once!
>
> > Yes, I couldn'
On Fri, Jul 13, 2018 at 8:39 PM Glenn Holmer wrote:
>
> [Sorry if this appears twice, T-bird crashed while sending.]
I only saw it once!
> Yes, I couldn't find it either. FYI, this was reported during NetCAT:
>
> https://issues.apache.org/jira/browse/NETBEANS-298
I'm not sure it's the same thing;
[Sorry if this appears twice, T-bird crashed while sending.]
On 07/13/2018 07:09 AM, Peter Hull wrote:
> On Fri, 13 Jul 2018 at 12:51 Alan Mathewson
> wrote:
>>
>> Yes, I've just reported the bug.
>>
> As a matter of interest, could you let us know the bug report number
> as I'd like to see how
On Fri, 13 Jul 2018 at 12:51 Alan Mathewson wrote:
>
> Yes, I've just reported the bug.
>
As a matter of interest, could you let us know the bug report number
as I'd like to see how it progresses?
I tried to find it on the bug report site but the search feature is
really limited.
Pete
---
Yes, I've just reported the bug.
I also get the same profiler crash with java 10.
From: Peter Hull
Sent: 13 July 2018 11:43
To: users@netbeans.apache.org
Subject: Re: Netbeans 9 profiler
On Fri, Jul 13, 2018 at 11:18 AM Alan Mathewson
mailto:mathew
On Fri, Jul 13, 2018 at 11:18 AM Alan Mathewson
wrote:
I get a very similar error on Windows 10 64-bit/Oracle JDK 10.
Did you also report it to the bugreport.java.com link given in the error
log?
Pete
hs_err_pid12032.log
Description: Binary data
Create new java application with main class.
Add System.out.println("Hello world");
Change java platform to java9 (properties).
Change source/binary format to java9 (properties).
Run profiler, methods, all classes.
profile:
Profiler Agent: Waiting for connection on port 5140,
Step by step instructions and then someone can try them out.
Thanks,
Gj
On Thu, Jul 12, 2018 at 5:36 PM, Alan Mathewson
wrote:
> Hi, I cannot seem to be able to run the netbeans 9 profiler properly.
>
>
> Telemetry and Objects(all classes) work fine.
>
>
> For Methods
31 matches
Mail list logo
