Any word on whether or not the ECM "perma-jam" some of us are experiencing is "working as intended" or a "bonus feature"?

If it's an intended feature, it's going to be a major detractor for anyone running anomalies solo. I don't know what Guristas missions are like in Empire, but I know the ECM is alive and well in northern 0.0 with a fury I've never seen before. Tengu + Dissolution Sequencer + ECCM stays permajammed for the first wave of a station Sanctum. I don't run anoms often (maybe once or twice a week at most) when I need a bit of extra liquid isk. When I do, I use a dual Tengu / Gila team to do it, assigning drones to the Tengu. Turns out that unless I send the Gila in first to take the ECM aggro, the Tengu with it's ridiculously high sensor strength is permajammed until those cruisers are eliminated. There's no way there could be such a permanent jam happening without a bug. The statistical mathematics of the jam formula, even taking the random number into accout, say it's impossible unless it's bugged.

So in the end, this doesn't affect me much at all as I have a workaround, but I do hope it gets addressed, as it's a real pain in the ass for people in general.

TIP OF THE DAY FOR CCP: If it's not broken, don't f@#ck with it.

Not just Chrome. Forcing to a new tab in Firefox does the same thing. Probably some onclick intercept not properly set up, which also means superfluous code to get a Web browser to do what it would have done anyway.

My only experience with it yesterday was in a L4 mission against Guristas. In the 4th pocket, i hit a spawn with 4 Dire Gurista Despoilers and 4 Pithi Exterminators. I was 95% perma-jammed. I had company along, so it wasn't as horrible as it could have been, but, i agree, the formula listed on the EVElopedia page suggests the chance of them successfully jamming me for that long in a battleship is highly unlikely.

Yeah. I can't remember offhand what my sensor strength is, but it's in the 40s, which is ridiculously hard to jam. A well skilled Falcon pilot with 3 racial ECMs modules only stands a 62% chance of jamming me at all with this fit, and it's been tested. Yet, the rats are getting a successful jam every time means there's something really wrong.

What is up with the suspisciously erratic loadtime of the client?

Sometimes it just sits there with the spash screen for 5-10 seconds.
It is a network thing? The CPU, disk and network is otherwise unoccupied.
Tried opening and closing the client 12 times, none of them felt like they were taking the same time.

And O M G, the cpu use of the browser (firefox) while typing in this box. Jumps up and down with 15%-20% spikes, then settles down then you take break from typing.
For comparison, massive spammy junktyping in wordpad can only bring it to 3%. Weird script **** must be going on.
Massive spammy junktyping here: brings a core up to 35% load.

And typing in other places on the net (blogs), does not present near the load that is going on here.

btw goddam, that is one long string. <input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="blabbla2mileslong".
That line (including tags) was 13433 chars long. What the hell is that.

Yep having the same issues with typing causing load on here. Maybe I type too fast ^_^

The Viewstate thing is a Microsoft .Net method of persisting the state of form controls. If they don't want to store it on their server then they pass it down to us in the shape of that hidden input field. Share the love.

Jesus. I just profiled this page in Firebug. It looks, to me, like the delays are caused in part by Firefox spending 25% of its time running a jQuery function called href, and also by the extreme number of AJAX postbacks that are going on. It looks like the typing window sends all that Viewstate back every 15 seconds with an average of 250ms roundtrip.

I assume this is because it's trying to autosave a copy of these precious words. And waste both CCP's and my bandwidth.

CCP - Please use a Javascript profiler like FIrebug for Firefox to show how much extra traffic/work is being produced! JQuery is great, AJAX is great, but you've gone a bit mental on them here!

And make my ship hover again, damn it.

I have been experiencing frequent crash-to-desktops since 1.4.1.
...stuff...