Crash on resume from standby - memory reference cannot be read
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- c
- Domain
- networking
Research direction
No source file or failing test is identified. Start by reproducing the failure under the listed Windows 10 and OpenVPN v2.8 conditions: sustain traffic, enter standby until Wi-Fi disconnects, resume, and use OpenVPN GUI's reconnect action; done means reconnecting without a crash.
Written by the indexing model from the issue text.
Description
Describe the bug
On resume from Windows standby/sleep (possibly related to "modern standby"), OpenVPN crashes with the following error:
The instruction at [address] referenced memory at [address]. The memory could not be read.
Click on OK to terminate the program
To Reproduce
Assuming this may be related to modern standby, ensure the PC has that functionality. Connect to a VPN, possibly related to having the VPN as the default route. Generally, this issue occurs after 800MB+ of traffic over the connection -- maybe more related to a long-life process (1 hour+). Put the PC to sleep for whatever amount of time is necessary for wifi to disconnect (5-15 minutes?). Upon resume, wifi reconnects. Open OpenVPN GUI and click the reconnect button. Under the correct conditions, though not always easy to reproduce, the process will fail with the above error message.
Expected behavior
OpenVPN should reconnect without failure after resume from sleep / modern standby.
Version information (please complete the following information):
- OS: Windows 10 IOT Enterprise LTSC 19044.7417
- OpenVPN version: v2.8 - build 64fbcb69a38b7ae6
Additional context
Thank you.
- Dominant language
- C
- Stars
- 14.8k
- Forks
- 3.4k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenVPN/openvpn
-
Difficulty 2/5 1-3 hours Newbie friendliness 71/100
-
CVE-2026-11604 vs OpenVPN 2.7.x DocumentationMay be free again @lstipakov claimed this 35 days ago, and no pull request is open. OpenDCO website Windows
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Document Real Address format change in management/status output (OpenVPN 2.7)Possibly taken A pull request linked to this issue is open or already merged. Opendocumentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Since 2.7.9 "route-method exe" can't set routePossibly taken @d12fk claimed this 1 day ago. Openoutdated code Windows
-
enhancement feature
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
issue: bug report
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Stellarium/stellarium#5197 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ChupathingyCE/chupathingyce#1550 ·
Maintainers usually reply within 1 day
-
[BUG] SWAPDB sends no invalidation to CLIENT TRACKING clientsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
redis/redis#16302 · 1 comment ·
Maintainers usually reply within 1 day