"Script Warning" popup with Search->AdvancedSearch

haertig · 09-30-2006, 12:15 PM

Interesting. A day or so ago I started getting the popup dialog box below when I click on "Search->AdvancedSearch". Anybody else seeing this? I haven't upgraded anything or changed any configs recently.

Code:

SCRIPT WARNING:

A script on this page is causing Mozilla to run slowly.
If it continues to run, your computer may become unresponsive.

Do you want to abort the script?

+------+    +--+
|CANCEL|    |OK|
+------+    +--+

I kill the script per the dialog box and everything procedes normally.

Using FireFox 1.0.7 (yeah, I know it's old) and Debian SID with 2.6.14 kernel. I do not have any Firefox extensions or plugins installed.

haertig · 09-30-2006, 12:21 PM

Additional info:

I now see this only happens when I first go to "Forums" using the upper nav bar and then click Search->AdvancedSearch from the nav bar.

This issue does not come up if I invoke the search after any other previous nav bar jump (e.g., to Home, HCL, Reviews, Tutorials, Articles, or MyLQ) It only happens if I first jump to "Forums", then invoke "Search->AdvancedSearch".

Nylex · 09-30-2006, 12:43 PM

I have also been getting this today, but I thought it was just me. It usually happens when I try clicking on "Quick Links". I'm using Firefox 1.5.0.7, with no extensions installed.

XavierP · 09-30-2006, 02:06 PM

I'm running Firefox 1.5.0.7 and can't reproduce the problem.

Nylex · 09-30-2006, 02:31 PM

Odd, it seems to have gone back to normal for me now :/.

Edit: nope, I'm still having the problem.

haertig · 09-30-2006, 02:41 PM

It's a 100% repeatable problem for me.

jeremy · 09-30-2006, 02:47 PM

How is it now?

--jeremy

haertig · 09-30-2006, 03:46 PM

No more problems for me. I just tried my repeatable failure scenerio about 6 times and it now worked perfectly every time!

It was a minor thing, and I was almost embarassed to bring it up, but thanks for fixing it!

jeremy · 09-30-2006, 06:08 PM

Thanks for the feedback.

--jeremy

Nylex · 10-01-2006, 12:02 PM

What was it that was causing the problem?