-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugcheck in ovpn_dco!OvpnTxBufferPoolGet #47
Comments
From what I see, TX pool is unreasonably large:
|
Portal incident id: 46108914 |
lstipakov
added a commit
to lstipakov/ovpn-dco-win
that referenced
this issue
Sep 25, 2023
- Handle case when IoAllocateMdl() and ExAllocatePool2() return NULL - Set max pool size (in-flight packets) to 100'000. This might help with OpenVPN#47 By playing with Quick Edit in console window (which makes execution stop) where iPerf3 was running I was able to get pool size growing to unreasonable values (over 50k). My understanding is that normally it should be <10k, but let's be on a safe side and cap it to 100k - in kernel dump it was over 1mil and system ran out of memory. Bump to 0.9.4. Signed-off-by: Lev Stipakov <[email protected]>
lstipakov
added a commit
that referenced
this issue
Sep 26, 2023
- Handle case when IoAllocateMdl() and ExAllocatePool2() return NULL - Set max pool size (in-flight packets) to 100'000. This might help with #47 By playing with Quick Edit in console window (which makes execution stop) where iPerf3 was running I was able to get pool size growing to unreasonable values (over 50k). My understanding is that normally it should be <10k, but let's be on a safe side and cap it to 100k - in kernel dump it was over 1mil and system ran out of memory. Bump to 0.9.4. Signed-off-by: Lev Stipakov <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: