Changes between Version 47 and Version 48 of DevelopersGuide

Timestamp:

2018-06-26T23:04:01+02:00 (8 years ago)

Author:

Don-vip

Comment:

add YourKit section with logo to get free license, see ​https://lists.openstreetmap.org/pipermail/josm-dev/2018-June/008072.html

DevelopersGuide

@@ -28 +28 @@
 * [http://www.youtube.com/watch?v=Z3OjG3nDvzA Video: how to checkout a JOSM plugin into Eclipse]
 
+=== YourKit ===
+{{{#!comment
+Do NOT remove the YourKit logo, this is required to get the free license, see https://lists.openstreetmap.org/pipermail/josm-dev/2018-June/008072.html
+}}}
+[[Image(yklogo.png, right, link=https://www.yourkit.com/java/profiler)]]
+JOSM core developers are using the [https://www.yourkit.com/java/profiler YourKit Java Profiler], as we found other tools lacking required functionality for profiling. YourKit supports open source projects by granting developers [https://www.yourkit.com/purchase/#os_license free licenses].
+
+To enable the YourKit Java agent, add the following JVM parameter:
+{{{
+-agentpath:<yourkit_path>/yjpagent.dll=delay=10000
+}}}
+
 === VisualVM ===
-VisualVM may be used to find memory leaks or generate heap dumps from a josm instance running concurrently. Heap dumps can be structurally examined. VisualVM organizes the dump data e.g. by number and type of objects, memory used and cpu time consumed in an explorable tree view. Heap dump and garbage collection of the target instance is requestable using button clicks.  Be aware that the default configuration of the memory sampler will sample VisualVM generated objects as well, which may be confused as a memory leak.  The memory profiler can be set to profile specific classes only, it tracks allocations once started.
+VisualVM may be used to find memory leaks or generate heap dumps from a josm instance running concurrently. Heap dumps can be structurally examined. VisualVM organizes the dump data e.g. by number and type of objects, memory used and cpu time consumed in an explorable tree view. Heap dump and garbage collection of the target instance is requestable using button clicks.  Be aware that the default configuration of the memory sampler will sample VisualVM generated objects as well, which may be confused as a memory leak. The memory profiler can be set to profile specific classes only, it tracks allocations once started.
 * [http://visualvm.github.io VisualVM]
 * [http://www.captaincasa.com/pdf/techdoc_memprofiling.pdf Step by step guide to memory profiling with VisualVM]