Proclaim 1.20.0.0026 - Proclaim.exe process burning 25% CPU when no application window

Page 1 of 1 (2 items)
This post has 1 Reply | 0 Followers

Posts 20
David Andrew Campbell | Forum Activity | Posted: Wed, Jan 29 2014 3:16 AM

Hi,

Proclaim got itself into a strange state today.  I don't know how to reproduce this but it happened.

What happened was that the software had been closed down, but Proclaim.exe was still running for a long time, burning 25% of the CPU.

Screenshot here:https://dl.dropboxusercontent.com/u/15033786/processes.png

Also, double-clicking the Proclaim icon wouldn't start Proclaim... I had to first kill the Proclaim.exe process and then start it again and then it started correctly.

Posts 3501
LogosEmployee
Scott Alexander | Forum Activity | Replied: Wed, Jan 29 2014 8:18 AM

It sounds like Proclaim was trying to finish doing something during shutdown and either hadn't completed it yet or got hung due to a bug. Proclaim ensures only a single instance is run at a time which is why you had to manually terminate the previous process before you could get it to start up. If you can get it to happen again and you grab the Proclaim.log file (while it is hung, before restarting) located at the location below then we can further diagnose the issue.

%USERPROFILE%\My Documents\Proclaim Log Files\

Page 1 of 1 (2 items) | RSS