Fixes have recently been made to improve profiling information when using -XX:+DebugNonSafepoints and tests have been added to validate it works correctly. See JDK-8201516.

We should consider enabling it when JFR starts, both from command line and jcmd.

If the user has specified -XX:-DebugNonSafepoints, it will not be overridden. This provides a workaround in case issues arise. If those issues can't be fixed, it's possible to revert to an earlier strategy.

Before committing a patch, we should measure how much additional native memory is being used.