[PR #349] [MERGED] Bugfix - IsaBusMutex Deadlock #1291

New issue

Closed

opened 2026-02-26 00:34:59 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 00:34:59 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/hirschmann/nbfc/pull/349
Author: @folfy
Created: 9/26/2017
Status: ✅ Merged
Merged: 9/27/2017
Merged by: @hirschmann

Base: master ← Head: master

📝 Commits (2)

48a4eb4 Bugfix - lost mutex deadlock
8f7c1e1 Merge remote-tracking branch 'origin/master'

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 Core/Plugins/OpenHardwareMonitor/Hardware/Ring0.cs (+1 -1)

📄 Description

If there is an abandoned Mutex (Exception; due to killing nbfc or some other application at the wrong time, or something like that, had this issue quite long time ago), acquiring it will fail in eternity (actually until a restart).

If this exception is thrown, acc. to MSDN we should be able to safely proceed:

The exception that is thrown when one thread acquires a Mutex object that another thread has abandoned by exiting without releasing it.

(Also going to suggest this edit to openHWMon)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/hirschmann/nbfc/pull/349 **Author:** [@folfy](https://github.com/folfy) **Created:** 9/26/2017 **Status:** ✅ Merged **Merged:** 9/27/2017 **Merged by:** [@hirschmann](https://github.com/hirschmann) **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (2) - [`48a4eb4`](https://github.com/hirschmann/nbfc/commit/48a4eb42520f8b2a3fe44a5bd4006066f0d1f2a8) Bugfix - lost mutex deadlock - [`8f7c1e1`](https://github.com/hirschmann/nbfc/commit/8f7c1e10f7ed52f575eacccda60bc43fdddaaeb9) Merge remote-tracking branch 'origin/master' ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `Core/Plugins/OpenHardwareMonitor/Hardware/Ring0.cs` (+1 -1) </details> ### 📄 Description If there is an abandoned Mutex (Exception; due to killing nbfc or some other application at the wrong time, or something like that, had this issue quite long time ago), acquiring it will fail in eternity (actually until a restart). If this exception is thrown, acc. to MSDN we should be able to safely proceed: > The exception that is thrown when one thread acquires a Mutex object that another thread has abandoned by exiting without releasing it. (Also going to suggest this edit to openHWMon) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>