problems removing more collapsed threads at once

RESOLVED INCOMPLETE

Status

Thunderbird
Folder and Message Lists
RESOLVED INCOMPLETE
9 years ago
8 years ago

People

(Reporter: Matěj Cepl, Unassigned)

Tracking

({perf})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [needs trunk retest] closeme 2009-12-01)

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; cs-CZ; rv:1.9.1b4) Gecko/20090427 Fedora/3.5-0.20.beta4.fc11 Firefox/3.5b4
Build Identifier: thunderbird-3.0-2.1.beta2.fc11

(originally filed as https://bugzilla.redhat.com/show_bug.cgi?id=498022)

If I try to remove more threads from my box, then the thunderbird3 isn't able
to move them into trash. If I remove f.e. three threads, then it's working.

Reproducible: Always

Steps to Reproduce:
0. set up an IMAP account
1. have many threads from some mailing-list in folder
2. select many of them and click Delete
3. see after a while warning about unresponsive script:
"A script on this page may be busy or it may have stopped responding. You can
stop the script now, or you can continue to see if the script will complete.
Script: chrome://messenger/content/folderPane.js:1137"
Actual Results:  
It's not possible to remove bigger amount of messages.

Expected Results:  
Delete will be working as it was in previous thunderbird2.

This is two or more bugs mixed in one, I am afraid:

1) only top of the thread message is deleted when key DELETE is pressed on the collapsed thread
2) JS/memory problem

Could you please untangle this and if possible deduplicate it against existing bugs?
Keywords: perf
Version: unspecified → Trunk

Comment 1

9 years ago
how many is many? In nightly builds for the past few weeks, deleting the top level message in a collapsed thread deletes all the messages in the thread, so you haven't been running the latest builds...

Updated

8 years ago
Whiteboard: [needs trunk retest] closeme 2009-12-01
RESO INCO due to lack of response to last question. If you feel this change was in error, please respond to this bug with your reasosn why.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.