> Again, as others have mentioned this does not appear to happen every time.
> You could try your test at various intervals during the parse, and after
> perhaps 10 or 20 times, see if it eventually causes the problem.

In case it helps folks understand things, the way the software works is this:
when you ask the parse/render to stop, the front-end sends a message to the
back-end asking it to stop. Until it stops the input file will remain locked
(if the parse hasn't ended, that is).

For some reason on some occasions the back-end isn't stopping the parse when
asked.

The front-end keeps track of the stop request and if you enter another one and
the previous one hasn't yet been honored, it stamps down a lot harder on the
back-end and abruptly terminates it. This is why a second stop request often
makes a difference.

As for why it's not stopping, well, we'll have to find that ...

Post a reply to this message