mkg335:
With users from all over the world using all kinds of browsers and comps experiencing similar problems, this has to be on wgt's end, something they've screwed up with flash deployment/interface I guess.
But like ct said, they've got plenty of time to implement unwanted and useless features like idiotic in-game comments and golfball tee markers.
Yes, totally agree mkg335..
The fact that the memory is reclaimed when you (or I) close and restart our browsers indicates that the memory leak is not a browser issue, but in this case a wgt game issue. If it were a browser problem, then the leaked memory would only be regained after a computer reboot.
My understanding of programming is that this is just a programming fault. In Java programming we were spoiled with "garbage collection", so memory leaks were not such an issue. In C++ programming not so, and you learned pretty quick to have routines to properly "clean up after yourself", to put it in layman's terms.
The problem as I see it is that the memory leaks not only cause the game to stutter like a strobe light, but I have also witnessed a lot more crashes (including the "!" crash) as the memory usage goes up.