-
Notifications
You must be signed in to change notification settings - Fork 168
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
High amount of spawn points causes crash #332
Comments
Actually it looks like it may still be related to this issue 2016-10-03 07:37:51,845 [ Thread-8258][ runserver][ ERROR] Uncaught exception IE this ticket (which I realize now was two diff issues, I DID fix the database locking issue but not socket issue) Which I thought I resolved by changing from sqlite to mysql, apparently this problem still occurs but ONLY if "show spawn points" are enabled. if disabled this issue is avoided. it seems it just cannot download the thousands of spawn points I have without crashing the socket and itself. |
if you have a LOT of spawn points. I'm talking thousands, app pretty much crashes instantly. Somewhere in between a lot and ok, it doesn't crash but moves VERY sluggish. Turning spawn points off can avoid crash and slowness. Spawn points in general need a lot of optimizing and crash fix, especially if #314 is added when scanning breaks.
The text was updated successfully, but these errors were encountered: