Skip to content

gist: fix socks5 udp#90

Open
DmitriyMV wants to merge 1 commit intoInterceptSuite:devfrom
DmitriyMV:fix-socks5-udp
Open

gist: fix socks5 udp#90
DmitriyMV wants to merge 1 commit intoInterceptSuite:devfrom
DmitriyMV:fix-socks5-udp

Conversation

@DmitriyMV
Copy link

Pull Request

Required Pre-Submission Checklist

  • I have read the CONTRIBUTING.md file
  • I have created a GitHub issue for this change and linked it below
  • I have forked the dev branch (NOT master)
  • I understand that the master branch is ONLY updated when a new release is created
  • I understand that pull requests to master will be REJECTED

Pull Request Details

Type of Change

  • Bug Fix Example

Related GitHub Issue

#89

Platform(s) Affected

  • macOS

macOS Application Changes

Does this pull request include changes to the macOS application?

  • Yes

Description of Changes

Right now if UDP receives empty message, it goes into hot loop (consuming entire core). This is probably not something that was intended. This PR provides an example of how it can be fixed, but I leave it to you how would you actually implement it. This PR simply demonstrates the flow that will probably be affected.

Fix is two part:

  • Close the udp session on error.
  • After the empty message wait at least 50ms before attempting again.

Compilation & Dependencies

  • I have reviewed the CONTRIBUTING.md file for compilation instructions
  • I have verified all required libraries and packages are documented
  • My changes compile without errors
  • My changes do not introduce new dependencies (or I have documented them below)

@DmitriyMV DmitriyMV changed the title DO NOT MERGE: Fix socks5 udp gist: fix socks5 udp Mar 12, 2026
@DmitriyMV DmitriyMV force-pushed the fix-socks5-udp branch 3 times, most recently from 6bfd62b to de3c283 Compare March 12, 2026 02:39
Right now if UDP receives empty message, it goes into hot loop (consuming entire core).
This is probably not something that was intented.

Fix is two part:
* Close the udp session on error.
* After the empty message wait at least 50ms before attempting again.
@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant