Crash on resume from standby - memory reference cannot be read

Open
#1,053 2 comments 0 reactions 0 assignees View on GitHub

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

bug Windows

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
Image

Thank you.

Dominant language
C
Stars
14.8k
Forks
3.4k
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenVPN/openvpn

All issues in OpenVPN/openvpn

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.