Annoyances during DNS resolutions since 1.9.8

[eregil]

Hello,

With NoScript 1.9.8 or 1.9.8.1 installed, I have annoyances during the roundtrip in DNS resolutions. Previous version 1.9.7.9 is not affected.

Steps to reproduce:
1) Open a site in a new tab. This can be done e.g. by middle-clicking (or right-clicking / open in new tab) a bookmark, or an external link on any site. Please note that since we're discussing something that happens during DNS resolutions, the site should be on a domain you haven't recently visited (to ensure that resolution is not cached) and that is not in your hosts file.

Symptom 1 (doesn't always happen): the tab appears later than usual. Up to NoScript 1.9.7.9 it was instantaneous or nearly so (depending on my CPU load), with NoScript 1.9.8 or 1.9.8.1 it sometimes takes a second or so for the tab to appear.

2) Quickly close the new tab before the name is resolved.

Symptom 2 (seems to always happen): when the name is finally resolved, the tab reappears (stealing focus) and the site is loaded. This is annoying because if I realize I have misclicked, I may want to close the tab so that the site is not loaded.

This is on a 64-bit Debian testing/unstable with Iceweasel 3.0.12. Please let me know if further explanation is needed, or if testing on different platforms is required.

Thanks for your continued development of this extension.

[therube]

I'll assume you have your browser set to switch to the new tab when you middle-click the link.

1) I can only say that there have been times when center-clicking a link appeared to do nothing (actually the browser appeared as if it were in a hung state) - temporarily. Few & far between, but I have seen it. Nothing to make me attribute it to NoScript, or anything else for that matter.

2) Not sure how I can do that? Open in tab, immediately followed by Ctrl+W is the best I can do. Hesitate for a moment & it is already resolved. In all cases, after closing the tab, nothing further ensued, except on one page, there was a popup that was fired (likely me just a bit slow in closing the tab itself) & that then did come up (seemingly) after the fact.

Nothing concrete that I am seeing.

Windows XP SP3, x86.

[eregil]

Yes, I have middle-click set to open new tab. Sorry if my previous post was not very clear.

As for 1), naturally, it can also happen simply due to CPU load, but it's just that the frequency of this behaviour seems increased to me when I install 1.9.8.x, so I was wondering if it happens to anyone else. It may be that NoScript 1.9.8.x is heavier on CPU, or something else may be happening.

As for 2), I could reproduce it on a Windows XP SP3 (32-bit) with Firefox 3.5.2 today, so it doesn't look platform- or Firefox-version-specific.

What you described as a popup firing may very well be the effect I described - in fact, the first time it happened I thought the popup blocking mechanism was misbehaving, but then, after a few occasions, I figured out that tabs were opening in the way I described in the first post. The behaviour is similar to that which was fixed in 1.9.7.9 with iframes being opened in new tabs - except, this time it's closed tabs reappearing.

It may be tricky to reproduce, because DNS resolution is usually quick, but I can reproduce it given a number of attempts, especially on heavy network load - and it will happen in my regular use of Firefox, sooner or later. I can try and make a screencast if requested.

[GµårÐïåñ]

You are not alone, I have noticed this too and using profiles without NS there are no problems. I am not sure if its how NS interacts with Fx core that is problematic or the problem is somewhere else and NS is triggering it or its just simply NS. I have been ignored on the issue for a while now across multiple posts and 6 different versions, so I have pretty much given up on the subject and given how poorly Fx has been performing, my Fx usage has been quite limited and therefore by proxy my usage of NS is nearly non-existent at the moment. Until stuff is fixed to function properly, I can't waste any more time on the Mozilla people and their products that don't work right.

[Giorgio Maone]

Could you check if your issues persist with 1.9.8.3?

[eregil]

Hi Giorgio, I have upgraded to 1.9.8.4 and it seems fixed, thanks!

[GµårÐïåñ]

Agreed 1.9.8.4 is better but 1.9.8.3 wasn't much different. Its still there but not as frequently or annoying as before.

[Alan Baxter]

@belainex:
I moved your psp question to its own topic: http://forums.informaction.com/viewtopi ... =18&t=3120

[Aleksej]

I see something like this on Debian stable (some packages are from testing/unstable) with

• NoScript 1.9.9.18 and 1.9.9.22 on Iceweasel 3.0.6-3
• NoScript 1.9.9.22 on Namoroka: successfully reproduced on Namoroka (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2b6pre) Gecko/20091214 Namoroka/3.6b6pre) and todays 20091215

Steps to reproduce:

1. Either:
   • Enter a URL of a site you haven't visited recently (maybe simply within this browser session).
   • Left click an external link to such a domain (at least such that will open in the current tab).
   • Try reloading the current page (could depend on the way you do it or on the time since the last resolution).
2. Wait a couple of seconds, but don't let anything load. (next day clarification: Do not let the page title appear.)
3. Press Escape.
4. Wait a few (approximately 2-4) seconds.

The link will load. If I press Escape after it started loading again, sometimes it will start again.

I haven't seen tabs reopen.

[Alan Baxter]

Unable to reproduce this problem on Windows XP SP3. Pressing Escape stops the loading, as expected. The link does not start reloading again. Pressing the Escape key a second time does nothing, as expected. I have to press the reload button to load the page.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2b6pre) Gecko/20091215 Namoroka/3.6b6pre
NoScript 1.9.9.22 with default prefs

[windy]

On Linux, using Firefox 3.6.3 with NoScript 1.9.9.81 still produces this bug. If I hit Esc during a DNS lookup that I know is going to fail (e.g. I've mistyped an address), the lookup stops at first but will continue after a few seconds. This does not happen with NoScript disabled.