Welcome to Microsoft Q&A!
t2 is in a tight loop of releasing and reacquiring the lock, which causes that the other threads (
t1 and the main thread) get no chance to acquire it, as Peter said.
Also see my answer about Slim Reader/Writer (SRW) Locks and the code.
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.