-
Notifications
You must be signed in to change notification settings - Fork 0
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
Chat-toolbox nonstop fetches comm data at high zoom levels. #26
Comments
Odd, I can't reproduce that locally, maybe it's a conflict with another plugin? |
Hmm. I tried disabling one of the plugins that I suspected could have interfered, but this plugin is still acting strange. Also extras tab shows how many messages are loaded and how long it took for the last draw event. Once it loads over 400 messages, it takes over 1 second for each draw event and that makes iitc extremely slow. Let me know if I can do something else to help troubleshoot this. |
Interesting, I was sort of able to reproduce the issue ... naturally once you start excluding large quantities of messages (in this case, large quantities of spam) there will be an increase in load requests as iitc itself tries to populate the chat log ... I'll have to give this some thought, but it might be limited by the fact we have to do everything client side Performance is something I have to work on... the biggest hit right now is probably regex creation, which I should be able to optimize |
Also, if I could get your IITC version, browser and browser version, and (probably unnecessary) plugin version that would be handy |
Windows 10, Chrome 56 (beta channel), iitc-test Version: 0.26.0.20170108.21815 (released yesterday). |
If I zoom out to a continent-level view, like
z=5
, for some reason this plugin causes my comm log to continuously keep fetching new data to the point where iitc becomes unresponsive.If I disable this plugin, things behave as expected.
The only exclude filter I have is
xmps\.biz|ingressfarm\.com|ingress-shop\.net|allforingress\.ecwid\.com|shop-ingress\.com|ingintems\.net
The text was updated successfully, but these errors were encountered: