"Failed to add PDH Counter" issues (caused by outdated OSHI)
I'm the primary maintainer of the OSHI project. There is a current dependency on oshi-core version 5.8.5.
I recommend you update to oshi-core version 6.2.1. (I realize this is a "New Feature" request and not a bug but the dialog did not give me any option to choose other than "bug".)
There has been a longstanding bug in OSHI regarding localization of performance counters. This has resulted in various secondary issues including slow startup issues associated with the WMI fallback and RPC delays. I had been doing either "all" or "nothing" on localization but only recently realized that "instances" still needed to be localized while "counters" did not. This bug was resolved in 6.2.1 in https://github.com/oshi/oshi/pull/2089
In addition to this fix, there is far better detection of disabled performance counters which will provide more useful/verbose log warnings to impacted users which will likely allow better self-remediation of issues without bug reports here.
Finally, this version includes the transitive dependency JNA 5.12.1 which significantly improves performance by removing finalizers. This reduces GC pressure and associated JVM overhead and promptly releases native memory allocations.
Created Issue:
Upgrade OSHI to resolve Failed to add PDH Counter issues
I'm the primary maintainer of the OSHI project. There is a current dependency on oshi-core version 5.8.5.
I recommend you update to oshi-core version 6.2.1. (I realize this is a "New Feature" request and not a bug but the dialog did not give me any option to choose other than "bug".)
There has been a longstanding bug in OSHI regarding localization of performance counters. This has resulted in various secondary issues including slow startup issues associated with the WMI fallback and RPC delays. I had been doing either "all" or "nothin" on localization but only recently realized that "instances" still needed to be localized while "counters" did not. This bug was resolved in 6.2.1 in https://github.com/oshi/oshi/pull/2089
In addition to this fix, there is far better detection of disabled performance counters which will provide more useful/verbose log warnings to impacted users which will likely allow better self-remediation of issues without bug reports here.
Finally, this version includes the transitive dependency JNA 5.12.1 which significantly improves performance by removing finalizers. This reduces GC pressure and associated JVM overhead and promptly releases native memory allocations.
I'm the primary maintainer of the OSHI project. There is a current dependency on oshi-core version 5.8.5.
I recommend you update to oshi-core version 6.2.1. (I realize this is a "New Feature" request and not a bug but the dialog did not give me any option to choose other than "bug".)
There has been a longstanding bug in OSHI regarding localization of performance counters. This has resulted in various secondary issues including slow startup issues associated with the WMI fallback and RPC delays. I had been doing either "all" or "nothing" on localization but only recently realized that "instances" still needed to be localized while "counters" did not. This bug was resolved in 6.2.1 in https://github.com/oshi/oshi/pull/2089
In addition to this fix, there is far better detection of disabled performance counters which will provide more useful/verbose log warnings to impacted users which will likely allow better self-remediation of issues without bug reports here.
Finally, this version includes the transitive dependency JNA 5.12.1 which significantly improves performance by removing finalizers. This reduces GC pressure and associated JVM overhead and promptly releases native memory allocations.
Upgrade OSHI to resolve "Failed to add PDH Counter" issues
relates to
Upgrade OSHI to resolve"Failed to add PDH Counter" issues"Failed to add PDH Counter" issues (caused by outdated OSHI)
is duplicated by
is duplicated by
MC-256086
I hate this bug, I have to wait 5 minutes every time t try to open the game.
Thank you for your report!
We're tracking this issue in MC-253901, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
New issue is tracked in MC-253901.
We have removed it and added the latest released version
Please edit the Affects Version/s field and select the specific Released Version you were using when you encountered the reported issue.
If you can't find it in the list, please make sure that:
This issue is being temporarily closed as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit
This is a feature request.
It is a summary bug for multiple bugs which have been reported here which you have resolved without fixing:
MC-245565MC-228430MC-228393MC-233152MC-228885MC-227785You will continue to get more bug reports like the above. Or you can take my word for it that there is a bug in your dependency which you can fix by upgrading.
https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Repository-keeps-restarting-Performance-Counter/ta-p/1716161
This fixed it for me