Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI not responsive - Infinite error loop #2796

Open
ochompsky opened this issue Oct 21, 2024 · 1 comment
Open

UI not responsive - Infinite error loop #2796

ochompsky opened this issue Oct 21, 2024 · 1 comment

Comments

@ochompsky
Copy link

ochompsky commented Oct 21, 2024

This isn't so much a bug as much as enhancement I think. If there is an unexpected error like this, the error loops infinitely:

10/20/2024 7:14:23 PM: LogUnhandledException - System.Exception: Get fan RPM speed Error: CTL_RESULT_ERROR_DEVICE_LOST
at Extensions.ThrowIfError(ctl_result_t result, String context)
at FanControl.IntelCtlLibraryPlugin.DeviceFan.GetSpeedRpm() in C:\projects\fancontrol-intelctllibrary\DeviceFan.cs:line 50
at FanControl.IntelCtlLibraryPlugin.DeviceFanPluginSensor.Update() in C:\projects\fancontrol-intelctllibrary\DeviceFanPluginSensor.cs:line 24
at FanControl.Domain.BackendProviders.Plugin.PluginBackendProvider.Update()
at FanControl.Domain.ComputerAccessLayer.Update()
at FanControl.Domain.ApplicationClock.DoActions()
--- End of stack trace from previous location ---
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate

I realize this particular error is because of the unreliable arc plugin and is more a symptom instead of the root cause. I saw a related issue at #2105

But in general, is it possible to make the UI not become completely unstable and fill up the logs when this happens? The error just infinitely loops and you can't click or do anything.

@Rem0o
Copy link
Owner

Rem0o commented Oct 21, 2024

I guess I could shutdown the whole provider/plugin when this happens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants