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

Hangs after walking to XXXXX until Ctrl + C is pressed to resume #827

Closed
iggut opened this issue Jul 25, 2016 · 6 comments
Closed

Hangs after walking to XXXXX until Ctrl + C is pressed to resume #827

iggut opened this issue Jul 25, 2016 · 6 comments
Labels

Comments

@iggut
Copy link

iggut commented Jul 25, 2016

Expected Behavior

Going to the next PokeStop and catching pokemon on the go

Actual Behavior

Bot hangs at Walking to XXXXXXXXX until I press Ctrl + C then it immediately starts encountering and catching pokemon and resumes running fine. It then hangs again after a couple minutes of running perfectly. Same way to kick it back into action.

Steps to Reproduce

Just let the bot run for 10 min to an hour and it hangs at a Walking to XXXXX until Ctrl + C is presset to resume for some reason.

Other Information

OS: Win 10 64bit
Running Dev version

@iggut
Copy link
Author

iggut commented Jul 25, 2016

I have not tried pressing anything else on the keyboard. Just though that it was the ctrl +c that woke it up, but might just be any keyboard activity. Will post update when it hangs again

@afro001
Copy link

afro001 commented Jul 25, 2016

CTRL+Z is also working and more safe, because sometimes when nothing was happening for a long time I pressed CTRL+C and accidentally stopped the script. With CTRL+Z there is no such problem. If there is a freeze - it resumes the script. If everything is ok - nothing happens.
How to get rid of these freezes? Windows 10, 64 bit here.
It is happening since the begining of my usage of this script, (last Friday) so should be not version dependent.

@iggut
Copy link
Author

iggut commented Jul 25, 2016

I can't figure out what causes it. Since right now I did nothing special and the bot has been running since it froze up when I finally posted this issue.

@Reaver01
Copy link

@fredrik-hellmangroup
Copy link
Contributor

not related to code, related to how cmd works by default in win10

@bsjpark
Copy link

bsjpark commented Aug 10, 2016

I am not sure if this will reopen this.
I am seeing exact same behavior on OSX El Capitan V10.11.5 Console as well.
Does anyone else see this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants