Quote:
Originally Posted by ownedbycats
Just a thought: if it happens again, what happens if you go to the task manager, right-click calibre.exe, and click ' analyze wait chain'?
A few times I've had issues with the generic InstallShield (used to swap out 16-bit stub installers on older games) getting stuck in the background until I close seemingly random programs such as Scrivener.
Attachment 198593 |
I did the T/ALT-f4 dance a few times until the problem happened with the editor. In Task Manager, I went to the Details tab and right-clicked on each of the three calibre-related tasks there (two calibre-parallel.exe instances (one of which appears to be the "stuck" one) and a calibre.exe instance). Selecting Analyze Wait Chain gave me pop-ups saying they were running normally.
I also saw several AMD related processes at the top of that list. Doing Analyze Wait Chain on amdow.exe gave me:
"One or more threads of amdow.exe are in waiting status:
- amdow.exe (PID: 11068) Thread: 11072
- amdow.exe (PID: 11068) Thread: 11104"
Of course, I don't know if that's related or if its expected (it continues to say that even after I shut down the calibre processes).
EDIT: I rebooted and checked that amdow.exe immediately thereafter. It still had those waiting threads. So, I assume it's just processing in the background and is expected.