fix: back reader/writer locks with a shared SRWLOCK wrapper#108
Conversation
|
Warning Review limit reached
More reviews will be available in 38 minutes and 43 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. 📝 WalkthroughWalkthroughThis PR introduces ChangesSrwSharedMutex introduction and migration
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
src/memory.cppinto a shared opaquedetail::SrwSharedMutex(include/DetourModKit/srw_shared_mutex.hpp) usable from public headers without exposing Windows headers.HookManager,InputPoller, and the module-range cache offstd::shared_mutex, which on MinGW is backed by winpthreads'pthread_rwlock_tand corrupts internal state under high reader contention.InputPoller::binding_count()read (now taken under the binding reader lock) and stopsInputManager::binding_count()from holding the lifecycle mutex across the poller call.InputManager.Summary by CodeRabbit
New Features
Documentation
Refactor