After all of the Perseus downloads, my indexer has been getting quit a workout. I noticed that my computer was still extremely sluggish even with indexing paused. No wonder—indexing is still running.
Seth Hewitt
Pausing does not completely stop the process by design.
Hmmm ... so pausing does not really pause by design. That's an interesting use of language.Is there any way to actually pause, or is the only option to permanently terminate the process by canceling it (assuming canceling actually cancels), or by killing the process?
Hmmm ... so pausing does not really pause by design. That's an interesting use of language. Is there any way to actually pause, or is the only option to permanently terminate the process by canceling it (assuming canceling actually cancels), or by killing the process?
The process is intended to keep running, but it should go as close to 0% CPU usage as it can.
No wonder—indexing is still running.
It could take up to a minute for the CPU usage to go down after pausing; so the fact that it has been paused for 14 minutes does indicate a problem. Was logging enabled at the time, and do you still have an Indexer.log available showing the process that you can attach to the thread?
