[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 113652] Hang up on attempt to edit field of existing entry
From:       Vincent DiCarlo <vdicarlo () dicarlolaw ! com>
Date:       2005-09-30 23:12:50
Message-ID: 20050930231250.30361.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=113652         




------- Additional Comments From vdicarlo dicarlolaw com  2005-10-01 01:12 -------
I've found some additional information. 

1. This only happens when you try to edit the address book (aka contact list in \
kontact) with the contact editor extension bar open. It does not happen if you open \
an edit window by clicking an entry with no extension bar selected.

2. Even with the editor extension bar open, it does not happen if you use the simple \
editor rather than the full editor.

3. The length of time the cpu is swamped is directly proportional to BOTH

  a. the number of entries in the address book, and 

  b. the number of characters you type into the entry filed of the editing box. for \
example, if i type a "t" into an empty field for "organization" with an address book \
of about 1,500 entries, it takes about 13 seconds to see the "t" in the field. If I \
type a "tt" in the box, it takes 26 seconds. I was wrong when I said above that the \
problem started as soon as you put the cursor in the edit field. It happens when you \
type the first character.

4. When I type into an edit field under the vulnerable conditions, and with a large \
address book of about 3,500 entries, I can see the list of contacts above the editor \
extension bar flicker.

Hypothesis: when you enter text under the vulnerable conditions, Kaddressbook \
attempts some kind of search through the records using EACH character that is typed.


[prev in list] [next in list] [prev in thread] [next in thread]