← Back to wkappbot-core
wkappbot-core ★★★

# Eye crash recovery via mutex force-release

When Eye crashes and cannot restart due to AbandonedMutexException, force-release the 3 named mutexes via PowerShell .NET API, then restart Eye. Eye revival also auto-clears zombie Chrome processes it owned.

user/developer

## Steps

1. DIAGNOSE STEP 1 — Symptom: wkappbot consoles...
2. DIAGNOSE STEP 2 — Confirm AbandonedMutex: ta...
3. DIAGNOSE STEP 3 — Confirm mutex still locked...
4. DIAGNOSE STEP 4 — Find mutex names WITHOUT s...
5. FIX STEP 1 — Force-release all 3 Eye mutexes...
6. FIX STEP 2 — Restart Eye: wkappbot-core.exe...
7. FIX STEP 3 — Console auto-recovery: wkappbot...
8. CHROME ZOMBIE — When Eye dies, it abandons h...
9. CHROME ZOMBIE ROOT CAUSE — Eye mutex Abandon...
10. HANDLE SCANNER — wkfix.ps1 -ScanHandles <pid...
11. NUKE PATTERN — wkfix.ps1 -Nuke <pid>: enumer...
12. CHROME SINGLETON — Chrome uses a named kerne...
13. SHORTCUT — wkfix.ps1 at D:/GitHub/WKAppBot/b...
14. ROOT CAUSE SUMMARY — Three bugs filed as sug...
15. FIND-OWNER PATTERN: zombie PID TerminateProc...
16. FIND-OWNER FIX: wkfix.ps1 -FindOwner zombie_...
17. FIND-OWNER FIX: wkfix.ps1 -FindOwner zombie_...
18. STRONGER THAN TASK MANAGER: wkfix.ps1 -Nuke...
19. STRONGER THAN TASK MANAGER: wkfix.ps1 -Nuke...
20. SELF-COMPLETING LOOP: FindOwner(zombie_chrom...
21. SELF-COMPLETING LOOP: FindOwner(zombie_chrom...
22. CHROME KILL ORDER: (1) Direct KillPid first...
23. CHROME KILL ORDER: (1) Direct KillPid first...

🔒 Pro Skill
Get Pro Access →