Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Keep alive after Chrome kill? #10

Open
ericlaw1979 opened this issue Mar 8, 2023 · 0 comments
Open

Keep alive after Chrome kill? #10

ericlaw1979 opened this issue Mar 8, 2023 · 0 comments

Comments

@ericlaw1979
Copy link
Owner

Chrome tries to terminate process on the NativeHost 2s after it closes the pipes. This used to be a no-op, but now that Chrome will directly talk to NM Hosts, it works. Should we introduce a dummy process to keep us alive for this scenario? Or should we just rely on the user doing a dummy batch file to avoid the termination?
ericlaw1979 pushed a commit that referenced this issue Mar 10, 2023
Add immortality
78b40b1 
Aimed to address #10, unfortunately it doesn't quite work because Chrome already has a handle with the TERMINATE right.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ericlaw1979