The active-settings view, used by 'jfr view' and 'jcmd view', takes the timestamp of the last ActiveSetting event and displays all settings that have the same timestamp.

This typically gives users a snapshot of the settings in use before a chunk or recording completes. In older recordings, ActiveSetting events were not emitted with the same timestamp, so you end up seeing only one setting for one event type. Also, if a single setting is changed programmatically before a chunk rotation happens, only that setting will be shown.

It may be better to just take the LAST setting. The drawback is that event types that have been unregistered during a recording may show up, but that may be acceptable.