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.

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

error in EnumProcessModules #23

Closed
timmcd opened this issue Aug 8, 2021 · 3 comments
Closed

error in EnumProcessModules #23

timmcd opened this issue Aug 8, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@timmcd
Copy link

timmcd commented Aug 8, 2021

I have been using an older version of Totsugeki successfully. Today I downloaded the v1.1.2 release and immediately tried to run it, and got this error. I thought it sounded a bit like a permissions issue so I tried running it as administrator, to no avail.

 _____       _                             _     _
|_   _|___  | |_  ___  _   _   __ _   ___ | | __(_)
  | | / _ \ | __|/ __|| | | | / _` | / _ \| |/ /| |
  | || (_) || |_ \__ \| |_| || (_| ||  __/|   < | |
  |_| \___/  \__||___/ \__,_| \__, | \___||_|\_\|_|
                              |___/
                                         v1.1.2
Starting GGST...
Started Proxy Server on port 21611.
Waiting for GGST process...
Error at offset 0x0: error in EnumProcessModules: Only part of a ReadProcessMemory or WriteProcessMemory request was completed.

It also opens a separate window...

image

@timmcd timmcd added the bug Something isn't working label Aug 8, 2021
@timmcd
Copy link
Author

timmcd commented Aug 8, 2021

v1.1.1 seems to work exactly as expected!

@optix2000
Copy link
Owner

optix2000 commented Aug 8, 2021

Thanks for the report!

I found this myself yesterday. It's an issue that happens when Totsugeki tries to patch GGST when the GGST process has started, but hasn't finished loading. Depending on the version of Totsugeki you use, the stars may or may not align to cause this issue (we're talking about a window of milliseconds).

This is fixed in 66e1d28. I'll cut a new release soon that should fix this issue.

@optix2000
Copy link
Owner

After looking at this more, there's actually a bug in v1.1.2 caused by the graceful shutdown, where loop for watching GGST was running without delays which is why this triggers 1000x more often on v1.1.2.

Definitely stick with v1.1.1 for now.

Thanks for testing the beta release!

@optix2000 optix2000 mentioned this issue Aug 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants