The award-winning all-in-one Java profiler for Mac

JProfiler for Mac

JProfiler 13.0.5

  -  148.39 MB  -  Trial

Sometimes latest versions of the software can cause issues when installed on older devices or devices running an older version of the operating system.

Software makers usually fix these issues but it can take them some time. What you can do in the meantime is to download and install an older version of JProfiler 13.0.5.


For those interested in downloading the most recent release of JProfiler for Mac or reading our review, simply click here.


All old versions distributed on our website are completely virus-free and available for download at no cost.


We would love to hear from you

If you have any questions or ideas that you want to share with us - head over to our Contact page and let us know. We value your feedback!

What's new in this version:

New features:
- Support for profiling Java 20
- Support for Hibernate 6.2
- Support for the Spring 6 WebFlux client
- Support for Apache CXF JAX-RS 4.0
- Added "Session->Save temporary session" to save a temporary session that is created when attaching to a JVM

Fixed:
- Regression in 13.0.1: On Windows, the progress dialog after the session startup dialog was shown outside the screen so the UI could appear as frozen during retransformations in attach mode
- Regression in JProfiler 13: The "Set as root" action was removed from call tree flame graphs, double-clicking to set a root also did not work anymore
- Regression in JProfiler 13: HTML export of graphs was broken
- Call tracer: The stack trace display could show wrong data when tracing multiple threads
- Call tree flame graphs: The header label always displayed the number of nodes and rows for the entire call tree and not for the current root
- Call tree flame graphs: Unrecorded times were shown as a flame graph node
- Kubernetes support: When using the attach action from an IDE integration, the "On a Kubernetes cluster" option did not work
- Kubernetes support: A custom location for kubectl was not applied when executing kubectl on a remote machine
- Executor tracking: Some calls were not tracked with third-party ExecutorService implementations
- Thread dumps in snapshots were not shown
- URL splitting with generic scripts did not work