Crispy™ Unresponsive Script on FireFox

[Western]

Was trying to brofist Taluntain but was prevented by lag, am taking this as a sign.

 

[Raapys]

This is unacceptable.

 

[cvv]

Lag. Sad. Fix plz.

 

[Severian Silk]

+1

 

[Angthoron]

I had to install script blockers to all my electronics now. I hope you're happy, Taluntain

 

[A user named cat]

Using Firefox 40, haven't experienced any script errors or lag here at all this week. You poor bastards

 

[Taluntain]

Could be a FF39 issue... anyone seeing it on non-Firefox browsers?

 

[cvv]

Testing FF40.

EDIT: Lag still there.

 

[Western]

Could be a FF39 issue... anyone seeing it on non-Firefox browsers?

Experiencing lag on chrome for Android.

 

[Dreaad]

Inb4 official statement "There was no downgrade."

 

[Angthoron]

Could be a FF39 issue... anyone seeing it on non-Firefox browsers?

Experiencing lag on chrome for Android.

Inbe4 we're told to reset our routers.

 

[Astral Rag]

Sounds like an overheating problem to me. Also don't forget to keep your GPU (Graphics Processing Unit) drivers up to date.

 

[Zep Zepo]

Clear cache
Update Java
Delete and reinstall TCP/IP Stack
Delete Temporary Files
Re-install DirectX

Zep--

 

[DarkUnderlord]

Taluntain, if we nix the VGLink for a few days, does it make it go away (IE: We sure it's this)? I've noticed it too. Particularly in the forum index - which makes me think it might also be a shoutbox conflict.

 

[Taluntain]

I'd have disabled it already but if it's something else on the Codex that's making it behave as it does, VigLink probably couldn't troubleshoot it. But yea, this has been dragging on for too long, I'll take it down for now. I'm seeing it with just threads open though, no shoutbox.

 

[Taluntain]

OK, the code's out and so's the lag from what I can see.

 

[Raapys]

WERE SAVED!!!!!!

 

[King Crispy]

I FEEL... YOUNG!​

 

[Kane]

OK, the code's out and so's the lag from what I can see.

 

[Angthoron]

Looks like it was a brofist harvest operation by Taluntain.

 

[Ulminati]

Could be a FF39 issue... anyone seeing it on non-Firefox browsers?

It made it 100% impossible to browse the codex on my android using chrome. Froze it up entirely.

 

[Taluntain]

VigLink have asked me to test the code again to see if they've fixed the issue, so if anyone spots any slowdowns again, please let me know. Especially those of you who've blocked it because you've actually experienced it, it'd be great if you could unblock so that we can verify if this has indeed been fixed for everyone.

 

[Zorba the Hutt]

Seems ok for me

 

[Angthoron]

VigLink have asked me to test the code again to see if they've fixed the issue, so if anyone spots any slowdowns again, please let me know. Especially those of you who've blocked it because you've actually experienced it, it'd be great if you could unblock so that we can verify if this has indeed been fixed for everyone.

So far so good, but will keep an eye on it when having multiple tabs open. When'd you reactivate it?

 

[Taluntain]

When I made the post above, so about 16 hours ago.