-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wgc: terminate called after throwing an instance of 'std::bad_alloc' #3060
Comments
It seems this issue hasn't had any activity in the past 90 days. If it's still something you'd like addressed, please let us know by leaving a comment. Otherwise, to help keep our backlog tidy, we'll be closing this issue in 10 days. Thanks! |
Not stale |
It seems this issue hasn't had any activity in the past 90 days. If it's still something you'd like addressed, please let us know by leaving a comment. Otherwise, to help keep our backlog tidy, we'll be closing this issue in 10 days. Thanks! |
Not stale. |
Is there an existing issue for this?
Is your issue described in the documentation?
Is your issue present in the latest beta/pre-release?
This issue is present in the latest pre-release
Describe the Bug
This only happens when the program is ran as
SYSTEM
, this is important because services are ran asSYSTEM
. Workaround for now, would be to either usecapture = ddx
, or run the program as the current user with Task Scheduler, anxml
file can be added to the repo, and imported with a script.287ac4c (wgc)
287ac4c (ddx)
Related:
Expected Behavior
If
wgc
can't be ran asSYSTEM
, a user check condition should be added, then throw, and there should be some relevant documentation regarding this.Host Operating System
Windows
Operating System Version
10
Architecture
64 bit
Sunshine commit or version
287ac4c
Package
Windows - portable
Capture Method
Windows.Graphics.Capture (Windows)
Config
The text was updated successfully, but these errors were encountered: