hovancik/stretchly

[Bug]: Error on Windows when starting app

Open

#1305 opened on Apr 17, 2023

View on GitHub
 (11 comments) (2 reactions) (0 assignees)JavaScript (3,892 stars) (410 forks)batch import
help wanted

Description

Version

  • I'm using version 1.14.0

Known issues

  • I've checked Known issues

Existing issues

  • I've checked Existing issues

Advanced Preferences

  • I've checked Advanced Preferences

What operating system are you using?

Windows

Operating System Version

Windows Server 2012 R2 Standard

Reproduction steps

  1. Installed version 1.14.0.
  2. Tried to open application.

... Reproduces how often: [What percentage of the time does it reproduce?]

Expected Behavior

I expected the application to open.

Actual Behavior

I receive the following error:

The procedure entry point DiscardVirtualMemory could not be located in the dynamic link library D:\Users\PRothenberg\AppData\Local\Programs\Stretchly\Stretchly.exe.

Relevant log output

No response

Preferences

No response

Additional information

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributor guide

Tech stack
javascriptnodejselectron
Domain
desktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic knowledge of Windows OSUnderstanding of Electron and native modules
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate the DiscardVirtualMemory API call error on Windows Server 2012 R2. This API is not available on older Windows versions, so the fix may involve conditionally handling the call or updating Electron's dependencies. Look into Electron's chrome sandbox or native module usage; consider adding a fallback or version check. Refer to Electron documentation on supported Windows versions and check if a newer Electron build resolves the issue.