InformAction Forums

When I have NoScript active and I visit page https://ib24.csob.cz/ Firefox just freezes. I tested few options:

1) Site is in my Whitelist, so nothing here
2) When I disable NoScript, everything works fine (although my back is tickling, I hate JavaSctipt enabled ).
3) When all extensions except NoScript are disabled, FF still freezes.
4) All this started about month ago, I am not exactly sure but I know site worked for me before. I have no clue whether site change or NoScript update cause this inconvenience.
5) I just realised that the site went through Java applet update around time it stopped working for me. But as in previous point, I am not exactly sure.

I hope everything sorts out.

Thanks for good work.

The site is quite slow but working fine for me.
Could you use the NoScript Options|Export button and then use "Reset" one?
If it works, please send me the exported file (which you could also use to restore the saved configuration) so I can check if there's a specific setting of yours causing the freeze.

I tried resetting NoSctipt and it worked ^^

Here is settings file: https://mega.co.nz/#!zx8QRC7Z!ICUohr90G ... yEtac8p-tI

Thanks a lot

SuperTukan wrote:I tried resetting NoSctipt and it worked ^^

Unfortunately it started freezing on me now, and resetting does not work for me.
I'm really puzzled: if it actually works for you now, could you please send me also your current configuration?

Thanks.

Well, here's backup of NoSctipt resetted settings: https://mega.co.nz/#!Tw8nwLQQ!JcMcoiHU7 ... U9227VVeX8. I tested it, worked (while all my other usuall extensions were active).

Ah, so it is not simply the fact that you have Allowed csob.cz, it is that you have actually placed it into your Whitelist.

Or no, that's not it either. But I know I have seen times where it has not locked up.

On on doing so, FF locks up, CPU is 25% (100% of 1 of 4 cores).

WhatIsHang report, FWIW, http://pastebin.com/nUnNqESJ.

Works now, thank you guys a lot!

Did we do anything?
When I looked originally it did work, then when I looked another time, I too had FF lock up.

So who knows if whatever was causing the underlying issue has actually been "fixed"?