Your testing and release engineering methodology is seriously flawed. The major problem with freeze-ups may be associated with the number of villages in a persons account but is definitely related to mismanagement of the caching on the end users platform. I get warning messages occasionally from chrome about lengthy delays in waiting for the cache. usually a few seconds before the browser freezes up. I would suggest looking into advanced custom caching solutions. Caching has been a long standing problem with your system. You need to redesign that entire part of the game. Concentrate on purging outdated items, some sort of in memory b-tree to access desired items quickly, custom indexes into the in memory cache db for specialized purposes, and a 2 generation scheme of caching with the 1st generation being new items that may be flushed soon and the 2nd generation being longer term items that may be hanging around for a while. There is a large body of knowledge around the internet about these techniques. Read up on them.
But all this just means on your test bed platform you need to test with a range of account sizes, and platforms corresponding to actual usage, The rule in testing is to test the edges of your domain space and then test mainline central average values.
The freeze up on the bulk building queue management seems to be slightly better. My observations.
1. Can actually perform 12-15 queue selections before the freeze occurs. But only if you are at the beginning of the page list or at the end.
2. If you are in a central page say you have 17 pages of villages and your on page 8 or 9 the freeze occurs after a single building selection.
3. The freeze seems to be related to the display or hiding of a buildings pop-up displaying resources and necessary resources with gold usage. Every freeze I have seen has been when a popup appeared or instantaneously after if disappears.
[Feature Request]
Please shade buttons that will invoke the expenditure of golds or the use of a inventory item with a different color. I suggest a red color. This allows users to see immediately which upgrades can be accomplished without spending some golds.
[General Rant]
I have been a programmer for thirty years and currently I am the Lead Engineer of a Big Data, Cloud Based, Analytics Platform doing Geo-Statistical Analysis of Agricultural data. I as at AT&T Labs for 12 years and Microsoft Labs for 5 years. I know how hard it is to build quality software. The biggest component of quality is having a thorough and systematic testing cycle. It is obvious that not even a cursory test cycle was run on this code. If any realistic simulation of actual users had attempted to use the major release features it would have been apparent in less than five minutes that this software was not ready to release.
In my experience it is better to release something late that works, letting the users be grateful that they have finally received an update than to release software that doesn't work and can actually damage a users position or game play. This is a failure of both the QA department and the upper management of the Dev team. Get your act together guys. I really enjoy this game but once you develop a rep for buggy releases you will see people leaving for other game systems. If you continue to do this you will eventually drive the game into the ground.
Sincerely,
Simon Brittanicus