🚀 go-pugleaf

I should have mentioned that I am seeing these behaviors with Code Guard on.

Jonathan Starr wrote:

> I have two issues:
>
> 1. thread suspend/resume
>
> If a low-priority thread is suspended, and a high-priority thread
> Resumes the low-pri thread but the high-priority thread continues
> to run, under what cirsumstances will the low-pri thread actually
> begin to execute?
>
> If the high-pri thread, while continuing to run, calls a thread method of
> the low-pri thread to Synchronize, will that make any difference (the
> high-pri thread should be the UI thread, and would call the other
> thread's method just to avoid duplicate code or complicated flow 
> control).
>
> Thanks in advance.
>
> PS What is happening is that the low-pri thread *appears* to begin 
> executing
> at a random point while the high-pri thread is busy again.
>
> 2. locking
>
> A thread may acquire a TCriticalSection a lock multiple times before 
> releasing it.  The
> lock maintains a counter internally.
>
> I had thought that if a thread acquired such a lock several times and 
> released it once,
> it still held it - another thread would block trying to acquire it 
> until it was released
> as many times as acquired.  But I am seeing a case in which a single 
> release seems to
> allow another thread to acquire the lock.
>
> Comments?
>