Comment 1 for bug 1815999

I do see a lock being taken and released in asCaStart() and asCaStop() around the signal/wait for asCaTask() to do its thing. This isn't easy to follow and certainly not how I would have written it, but in conjunction with the RCU-like approach to modifying the volatile ASBASE *pasbase in asLibRoutines.c and the LOCK/UNLOCK pair in asInitialize() I suspect there is enough here to prevent races.

No objections to it being rewritten, but I don't see it as a priority.