Closed Bug 35796 Opened 25 years ago Closed 25 years ago

dialogue box slow

Categories

(SeaMonkey :: General, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: spam, Assigned: asa)

References

()

Details

2000-041309 M16 when clicking link "Other Nightly Builds" it takes 78 seconds before the dialogue box appears with "Are you sure..." etc. Worse yet: Dismiss the box and click again: It takes 78 seconds once again. On NS4.7 the dialogue box appears instantly. Tested in a P120.
For what it's worth - perhaps a clue: There was recently another quirk with that link, but couldn't reproduce so changed to "works for me". See bug 35282
What is the output to stdout when you click on that link (check in ther terminal window you used to start mozilla). I got something like this: WEBSHELL+ = 12 WEBSHELL+ = 13 WEBSHELL+ = 14 commonDialogOnLoad << the box appears Move window by 55,94.6 screen x 131screen y 153 << I click OK/Cancel WEBSHELL- = 13 WEBSHELL- = 12 WEBSHELL- = 11 I can imagine if Mozilla has been running for a considerable time and the value for webshells is fairly high then this could take a long time.
Weird. If i keep the cursor positioned OVER the link after i click on it (and let go of the mouse) - it will take 78 seconds before the popup-box appears. If i move the cursor AWAY from the link, it will take 15 seconds. Still a very very long time though, but this smells "threadsafe something". The test now was after starting moz afresh with about:blank and going right to http://www.mozilla.org/binaries.html The output you asked for indicated 4 webshells open before clicking link.
There is a third type of behaviour involved as well. Resummarizing: 1: Click link, keep cursor over link: Dialogue pops up after approx. 80 sec. 2: Click link, move cursor away from link out on page: pops up after 15 sec. 3: Click link, move cursor away from link and over another link so the cursor changes shape to pointing hand: box pops up after "only" 4-5 sec. Even in the "best case" here it's over 10 times slower than NS4.7 which pops up the box in a fraction of a sec. Anwyays - users can't be expected to shake their pointing devices (even if tempted) in order to make the browser move. This last round was tested on a new build: 2000-041316.
With 2000-04-13-08-M16 on WinNT, the alert appears within 1/4 second.
sidr@albedo.net - please test it once again, like this: Exit all of Mozilla Restart the browser Go right to http://www.mozilla.org/binaries.html THEN do the test as described in my previous comment. (holding cursor over link etc)
You see..i discovered that if i in advance have had mailnews open and fetched mail, this bug doesn't get appearant. And what happens when i get mail is that a dialoguebox prompting for master-password appears and is filled in. Something regarding dialogueboxes isn'nt getting initiated right when their first "date" is a link. Nor is it "remembered". But when password dialogue has been forced to occur, it gets initiated the right way, moz later "remembers" what they are, and carry that memory with it when new instances of dialogue-boxes are called for. OR something like that ;) (As you realize i'm not a programmer.) This may still be platform dependant of course.
Retested on WinNT; results as before for each of the 3 variations, roughly 1/4 second until alert shows up -- more than 1/10, less than 1/2, for certain. This is looking likely to be [PP], linux-specific.
Well this place reaks with linux users and noone has been able to confirm this so i'm setting it invalid. Dupes aren't far between so if this is a real problem it will be submitted again. Sorry for the spam.
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Reinstalled with a new profile. I can repeat this EVERY time. Just in case it was unclear: Do NOT move the cursor after the link is clicked. Leave it exactly where it was. Please reopen this - it's very real. Bugzilla won't let me reopen owen bugs it seems :)
never mind - i'm opening a new bug about this instead. Leave this one as is.
dark@c2i.net, the proper resolution if nobody else can reproduce a bug and you can't any more either is WORKSFORME. But since you still could, it's better to wait a day or two and try other builds. You could also try asking someone on the list at http://www.mozilla.org/quality/help/mozilla-testers.html to try it out. In any case, you should have been able to change the STATUS on your own bug, but it seems that there have been random glitches in Bugzilla lately... I had a change not take myself yesterday, and at lest two other times in the last week. For Reference, the new bug is bug 35884, "dialogue box extremely slow". VERIFYING.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.