Fully featured low overhead profiler for Java EE and Java SE platforms.
Performance monitoring and profiling of Jenkins, TeamCity, Gradle, Maven, Ant, JUnit and TestNG.
Easy to use performance and memory profiler for .NET framework.

.NET 4.0 issues

Moderators: Vladimir Kondratyev, Anton Katilin

.NET 4.0 issues

Postby edrishn » Thu Feb 07, 2013 7:29 am

First of all thanks for your .NET profiler and Probes feature which is a nice addition.

in all 8.0X releases (including 8.03):
- if you enable 'Probes' when Profile 'Standalone Application'
- if you 'Connect to Application'
Profiler (javaw.exe) crashes

I tested with different settings and different applications with same results.
After installing Visual Studio 2012 (.NET Framework 4.5) those problems gone away.

As you know .NET Framework 4.5 is in-place upgrade so debugging applications and reproducing bugs with .NET 4.0 applications won't be possible after installing it:

It seems .NET Profiler incompatibility with .NET 4.0 is also related to this problem. It means although you selected '.NET Framework 4.0' as 'Target Framework', 4.5 will be used when you debug .NET Profiler.

Any chance to support .NET 4.0 in further releases?

P.S. Please keep developing your .NET Profiler which is the best specially in terms of UI and Performance.
Posts: 4
Joined: Thu Feb 07, 2013 6:42 am

Re: .NET 4.0 issues

Postby Anton Katilin » Thu Feb 07, 2013 10:02 am


Thank you for reporting this issue and for your kind words about the profiler.

This is a new issue.

Could you please provide the crash details. In particular, we are interested in the log files in <user home>\.ynp\log

Under which Windows version did you get the crashes?

Best regards,
Anton Katilin
Posts: 5709
Joined: Wed Aug 11, 2004 8:37 am

Re: .NET 4.0 issues

Postby edrishn » Sat Feb 09, 2013 4:43 pm


Excuse me for late reply.

Operating System is Windows 7.

Log files when profiling freely available program LINQPad sent to support@yourkit.com

Posts: 4
Joined: Thu Feb 07, 2013 6:42 am

Re: .NET 4.0 issues

Postby edrishn » Tue Feb 12, 2013 8:09 pm

Based on e-mails back and forth between me and Anton:
It seems my case is specific to some computers and changes done in 8.02 resolved Probes issue with .NET 4.0 in general.

I invite other users with a similar problem to continue this thread and send logs for further tracking down this issue.

Thanks for your support,
Posts: 4
Joined: Thu Feb 07, 2013 6:42 am

Return to .NET Profiler

Who is online

Users browsing this forum: No registered users and 3 guests