Closed
Bug 953754
Opened 12 years ago
Closed 3 years ago
Selection serialization horribly slow when thousands of messages are selected
Categories
(Instantbird Graveyard :: Conversation, defect)
Instantbird Graveyard
Conversation
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: florian, Unassigned)
References
Details
*** Original post on bio 311 at 2010-01-20 17:13:00 UTC ***
The current selection serialization algorithm does a full tree traversal on the subtrees touched by the selection. When thousands of messages are selected, this is very slow (with 5000 messages, the application is frozen for tens of seconds, of not even minutes!).
We should optimize so that we only walk through the DOM at the start and end of each selection range.
We want to go from O(n) to O(1). (n being the number of selected messages)
In order to do this, we need to be able to get a list of all the messages between 2 messages, so we need to have information about all the messages displayed (bug 953743 (bio 300)).
Warning: messages can be nested (when div id=insert is inside the previous messages' content).
Fixing this is not required for 0.2 because now that we have a log viewer, there's an easy workaround for someone who wants to copy/paste the content of a whole very long conversation.
Comment 1•3 years ago
|
||
Instantbird and Instantbird Servers products have been graveyarded. These bugs will no longer be looked at and are being closed.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•