203945 - Type down in compose window very slow resulting in very slow auto complete

Status: VERIFIED FIXED

(MailNews Core :: Composition, defect)

Description

[esther]

Using trunk builds 20030429 on winxp and macosx (haven't tested linux yet)
typing in the Compose window has regressed in speed and I consider it very slow.
 This started in the 4-29 build, 4-28 is OK.  I'm not sure if this is auto
complete or type  down that is causing the problem.  My personal address book
has 135 addresses, Ninoschka had 20.  Neither of us have any addresses in
collected address book, and I have tried this with LDAP on and off (LDAP doesn't
seem to affect this), Ninoschka doesn't have an LDAP set up.

1. Launch app (have at least 20 addresses in your address book that you can
autocomplete against) 
2. Log into mail
3. Bring up a Compose window 
4. Type (1) character that should bring up a match (with 4-29 build this took 4
sec to auto complete, with 4-28 build it was instant)
5. Xclose the compose window and launch another compose window
6. Type (3) characters wait for auto complete, takes longer
7. Repeat steps 3,4 &5 adding more characters, deleting some then adding more.

Result: Progressively slow response when typing characters and then very slow
autocomplete.

Comment 1

[esther]

adding keywords and reassigning. 

Comment 2

[esther]

I just tested this with autocomplete off, the typed text is appearing as typed
so this is caused by autocomplete. 

Comment 3

[sairuh (rarely reading bugmail)]

could this be related to the fix for bug 173430?

Comment 4

[[e-mail]]

caillon: maybe fixed by your latest dirprefs epiphany?

Comment 5

[(not reading, please use [e-mail] instead)]

I just started looking into this, but my guess it isn't related to callion's change.

will know more soon.

Comment 6

[esther]

More info, it seems that this only happens if you have a list in your address
book.  deleting all my lists the auto complete work fine. 

Comment 7

[Christopher Aillon (sabbatical, not receiving bugmail)]

Seth, actually I think this might be mine as well.  After pouring over the code
yet again last night, I noticed finally that I forgot to weed out dupes in the
child lists that we create, so we are looping over extra stuff.  I believe that
is also what caused bug 203859.  Working on a patch now to test.

Comment 8

[(not reading, please use [e-mail] instead)]

re-assigning to chris, since this and bug #203859 were caused by the fix for bug
#173430

Comment 9

[Christopher Aillon (sabbatical, not receiving bugmail)]

Fix for this bug attached in bug 203859.

Comment 10

[Christopher Aillon (sabbatical, not receiving bugmail)]

Fix checked in.

Comment 11

[Christopher Aillon (sabbatical, not receiving bugmail)]

*** Bug 204081 has been marked as a duplicate of this bug. ***

Comment 12

[esther]

Tested with build 200305002 on winxp, macosx and linux this is fixed. Verified.

Comment 13

[Mike Cowperthwaite]

*** Bug 204078 has been marked as a duplicate of this bug. ***