Originally Posted by
gorco15
How do you download this?
Click the download link at the bottom of post 12 in this thread.
flowing_around, there's some sort of memory leak in get_proc. When left at "searching for hng ...", the system leaks about 1.5 GB of memory per minute. I left the program running after a match and had about 15 seconds notice between Windows telling me my system was out of memory and half the processes on my system crashing.
I'm not very familiar with the Windows APIs or C++, but I think this is because the program calls get_proc with no sleeps in between (using 100% of a CPU core while it's at it), and never calls CloseToolhelp32Snapshot on the snapshots; see the remarks at msdn.microsof*****m/en-us/library/ms885189.aspx (no link because I'm not allowed to post links but text representing a link is apparently fine this forum is stupid)
I think closing the snapshots will fix the memory leak, and adding a 250ms sleep between calls to get_proc should bring the CPU usage down a lot.
Edit: Oh yeah, the program only seems to work for one round before it needs to be relaunched. Once the second match starts loading, it just loops the following:
Code:
hook to hng ... searching modules ... <<-- Done
enabling show projectile path ... | failed
error log: try again or ur out of luck
searching for hng ... | Done
Closing and relaunching the program gets it working for that round.