82317 - Addressbook auto-complete hangs system

Status: VERIFIED INVALID

(SeaMonkey :: MailNews: Address Book & Contacts, defect)

Description

[Sean Su]

While in the mail compose window, I start typing the first characters of the
recepient.  The autocomplete engages and begins providing a list of people that
starts with the characters I typed so far.

While it looks for all the names, and at the same time it's displaying them, I
hit the down-arrow key to start scrolling.  The "hang" happens here.

I should also point out that I had previouly changed the preferences from the
default settings:
1) go to "Edit | Preferences | Mail and Newsgroups | Addressing"
2) check the "Directory Server" check box.
3) click on the "Edit Directories" button
4) click on the "Add" button.
5) for the Name field: Netscape Personal
6) for the Hostname field: nsdirectory.netscape.com
7) for the Base DN field: dc=com
8) click okay to save it
9) select "Netscape Personal" that you just created
10) click okay to save it
11) make sure "Netscape Personal" is selected as the "Directory Server"
12) click okay to save it.

This is running WinMe using the commercial build: 2001-05-22013

The workaround is to let it finish looking up (and displaying) all the names
that started with the characters I typed.  The the down-arrow works fine.
FWIW: the characters I started typing to cause this bug is: "syd"

Also once the list of names is fully loaded, the scroll bar is buggy.  Clicking
on the down and up arrows work fine.  Clicking on the space above and below the
scroll bar works fine.  Clicking and trying to move the scroll bar makes the
scroll bar jump back to the top of the list (if scroll bar is not at the top of
the list).

I can file a seperate bug on this if you want me to.

Comment 1

[chuang]

This seems to be the dup of bug 82136.  Sean, can you look at bug 82136 and try
again.

Comment 2

[Sean Su]

Under NT4 (sp6) at LAN speed, I cannot reproduce bug 82136, nor this bug with 
build 2001-05-22-13, which has a build id of 2001052204.

This bug was origianlly filed against WinMe.  I was also connected via 56k modem 
(this might make a difference).  I will try to reproduce both bugs with Win98 at 
LAN speed.

Comment 3

[Sean Su]

Under Win98, LAN speed, both this bug and bug 82136 are not reproduceable.  I 
will try again under NT4 (sp6) via 56k modem later tonight.

Comment 4

[Dan Mosedale (:dmosedale, :dmose)]

Almost certainly an LDAP problem in the C SDK (async connect not working, bug
79509) or the XPCOM SDK (async DNS not used, 82412).  I've made those two bugs
block this one; taking.

The buggy scrolling thing should indeed be a separate bug.

Comment 5

[Oliver Klee]

Upping severity to Critical and adding hang keyword.

Comment 6

[fenella]

I cannot reproduce this problem using the Win32 (2001-05-30-04-trunk)on win_nt 
4.0.

Comment 7

[Dan Mosedale (:dmosedale, :dmose)]

Now that 82598 is fixed, this requires more effort to reliably reproduce.  To
reproduce the DNS hang case (bug 79509), you'll need to somehow block the DNS
server from answering; to reproduce the connect() case (bug 82412), you'll need
to somehow block the LDAP server from answering.

Comment 8

[Sean Su]

This doesn't hang on me like it did before.  I tried it a home on the same 
machine.  But I can't use the enter key to select what is hilited.  This is 
probably a different bug.

I'm okay with this bug marked as fixed.

Comment 9

[Dan Mosedale (:dmosedale, :dmose)]

Note that the instance ssu hit is probably fixed, but the others are not.  Let's
leave this open as a meta-bug.

Comment 10

[Eric Hedström]

Using LDAP autocomplete the last few days, I have had crashes sometimes, but
also Mozilla often consumes all the CPU cycles until you kill it. It's not a
hang because it keeps responding to input, but some thread keeps using all the
CPU it can get. Not sure if this is related to this bug or 79509 or..

Using win32-installer 2001060409 on win2000 right now, LDAP server is MS Exchange.

Comment 11

[Dan Mosedale (:dmosedale, :dmose)]

Erich: sorry for not responding to this sooner.  If the crashes can not be
easily reproduced, the best thing you can do is run talkbalk-enabled nightly
builds.  Then if it crashes, file a bug in bugzilla and reference the talkback
incident id.

Note, however, that the CPU memory hogging bug should be fixed, and all known
crashers in LDAP autocomplete have been fixed, so with luck this won't be an
issue any more.  :-)

Comment 12

[Eric Hedström]

Dan, thanks for all the work you've done on the LDAP support, it makes mail much
more useful at work.

I haven't had any crashes recently, but I opened bug 85452 for the cpu-sucking
case because that does still happen using nightly talkbalk win32-installer
builds. What's the easiest way to see what it's doing with all that cpu time
short of snarfing the source from CVS and building locally? Am I the only one
seeing that?

Comment 13

[Dan Mosedale (:dmosedale, :dmose)]

I _think_ the behavior you're seeing may be fixed in more recent builds.  See
the commentary that I added to 85452, and we can continue this discussion there.

Comment 14

[fenella]

Yulian, I am going to route it to you since it involves LDAP. If you disagree,
please let me know.

Comment 15

[Dan Mosedale (:dmosedale, :dmose)]

I don't think keeping this open as a meta-bug is really very useful, since
there's now only one bug that depends on it.  Resolving.

Comment 16

[yulian chang]

v