Bug: Indexer in 4.3 SR-5 (4.30.0.1603) does not stop when paused

Page 1 of 1 (5 items)
This post has 4 Replies | 0 Followers

Posts 91
Seth Hewitt | Forum Activity | Posted: Thu, Oct 6 2011 7:52 PM | Locked

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

Posts 4077
Melissa Snyder | Forum Activity | Replied: Mon, Oct 10 2011 3:35 PM | Locked

Pausing does not completely stop the process by design.

Posts 82
David L Adams | Forum Activity | Replied: Wed, Oct 12 2011 6:14 AM | Locked

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?

 

Posts 4077
Melissa Snyder | Forum Activity | Replied: Wed, Oct 12 2011 10:54 AM | Locked

David Adams:

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.

Posts 4077
Melissa Snyder | Forum Activity | Replied: Wed, Oct 12 2011 10:57 AM | Locked

Seth Hewitt:
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?

Page 1 of 1 (5 items) | RSS