> Such a task is usually thankless work so, thank you. :) It's just a game of whack-a-mole, finding new segmentation faults and other bugs is quite easy when

> Such a task is usually thankless work so, thank you. :) It's just a game of whack-a-mole, finding new segmentation faults and other bugs is quite easy when you know how to write good test code. Fixing the actual bugs less so. But it's fun and I do this for a living in the SapMachine team at SAP SE. > I don't doubt my favorite profiler, YourKit also uses your code. They surely do profit by work improving the profiling APIs. > Just a cursory glance can quickly verify assumptions about runtime performance. Yes. But there aren't enough people educating people on profilers. So I started blogging and talking (https://youtu.be/Fglxqjcq4h0 https://youtu.be/Fglxqjcq4h0) on this topic. Besides fixing all the bugs and implementing my own profile viewer based on FirefoxProfiler (https://plugins.jetbrains.com/plugin/20937-java-jfr-profiler https://plugins.jetbrains.com/plugin/20937-java-jfr-profiler).