The current TAS client is violently unstable

[SwiftSpear]

After playing a few games and trying to host a few games (which my firewall blocked ) at some point when I tryed to load the battleroom the TAS client would become unresponsive and start using 50-70% CPU power. initially closing the client and loading up again would allow me to load the battleroom, but after the next crash I had to restart my computer to fix the problem. Now even restarting doesn't work. The battleroom simply won't load.

I'm gonna play around with settings without really knowing how things work and see if I can restore stability to it, at least on a temporary basis, but I find it frustrating that the new version doesn't work when the old one's did.

[edit] any advice on a fix would be great

[edit2] after testing it seems to be related to closing the server browser improperly (pressing the x in the topright corner without disconnecting from the server) and apparently is fixable by creating and disconnecting to a server you hosted yourself.

[Doomweaver]

What browser are you using?

[SwiftSpear]

Umm... the updated TAS client that I DLed off the front page just recently...

[deadram]

Ummm... your problem may just be a poorly implemented GUI. The net code and the GUI are ~NOT~ in separate threads. Basically what that meens is nothing happens asyncronously (at the same time). So the app starts up, freezes, and makes a DNS request for the server IP, initiates a connection to the server, then unfreezes and updates the display. If your DNS server is slow, or the battlenet server is laggy, then this initial "freeze" could take upwards of 30 seconds. Along with that, much of the actions (such as joining a game) may cause temporary "freezes". I've already mentioned a thread client would work best, but since 1 of the few fixes to the TA source code that I've made have been fully intergrated into TA I've stopped development for TA. I think if you want a solution you should try to bug the develepment people about bug.

[SinbadEV]

** Kick's Ded in the Head... WAKE UP!!! **

[SwiftSpear]

Ummm... your problem may just be a poorly implemented GUI. The net code and the GUI are ~NOT~ in separate threads. Basically what that meens is nothing happens asyncronously (at the same time). So the app starts up, freezes, and makes a DNS request for the server IP, initiates a connection to the server, then unfreezes and updates the display. If your DNS server is slow, or the battlenet server is laggy, then this initial "freeze" could take upwards of 30 seconds. Along with that, much of the actions (such as joining a game) may cause temporary "freezes". I've already mentioned a thread client would work best, but since 1 of the few fixes to the TA source code that I've made have been fully intergrated into TA I've stopped development for TA. I think if you want a solution you should try to bug the develepment people about bug.

A: should these "freeze times" cause constant 50% cpu usage while they are in loading?

B: shouldn't it eventaully unfreeze? because it doesn't it just outright crashes the client software to the point where the only fix is to reboot it.