You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the past two days, I did a stress test for npcap. It was found that when the network speed exceeded 400Mbps, npcap could not work normally. The number of packets captured was zero for a period of time, and it would run out of memory. I switched wireshake's packet capture and found that the same phenomenon occurred。
The text was updated successfully, but these errors were encountered:
Thanks for this report! We have been working closely with a licensee who was seeing the same issues, and we expect to have a release out to address it soon. The essence of the issue is an integer underflow in the count of "free" space in the kernel buffer, and the fix is in 5abba5e, but there are lots of related changes that will go into the release.
In the past two days, I did a stress test for npcap. It was found that when the network speed exceeded 400Mbps, npcap could not work normally. The number of packets captured was zero for a period of time, and it would run out of memory. I switched wireshake's packet capture and found that the same phenomenon occurred。
The text was updated successfully, but these errors were encountered: