76691 - Send empty trash/expunge inbox processes to a separate, background process?

Status: RESOLVED DUPLICATE of bug 401295

(MailNews Core :: Backend, enhancement)

Description

[Troy Telford]

I use IMAP for email.

I have my mailbox set to empty trash on exit, and expunge inbox on exit of
mail/news.

When I close the mail window, mozilla becomes unresponsive for a period of 15-20
seconds after I attempt to close the window; after that time the mail/news
window closes, and mozilla becomes repsonsive once again.

I figure this is due to the mail/news client executing the 'empty trash' and
'expunge inbox' commands before closing the mail/news window, which locks up the
rest of mozilla until those commands are complete.

In Netscape 4.x, a seperate window and process was opened that displayed this
process, while the mail closed immediately, and full control was returned to the
browser.  The 'cleanup' window displayed its progress and status while it
cleaned the trash on the various mailboxes.  It did not interfere with normal
browsing, and closed itself when finished.

However, in Mozilla, no such window exists, and the mail/news window remains
open until it is done emptying trash, and expunging the inbox.  No
progess/status is displayed, and suspends all other access to the browser until
mail/news is finished with its empty trash/expunge inbox operation(s).

It would be nice should Mozilla have a similar behavior to Netscape 4.x in this
respect; in that:

*mail/news immediately closes
* a seperate, background process is spawned that:
  * opens a status/progress window displaying empty/expunge status.
  * handles emptying trash/expunging inbox.
  * does not interfere with normal browsing (doesn't lock browser until it's done.)

Comment 1

[Scott MacGregor]

david, don't you already have a bug about us pinging the CPU when expunging the
trash folder on exit?

Comment 2

[David :Bienvenu]

yes, but we can't do what the reporter wants because we have to assume that the
whole app is shutting down, not just our mail window. And if we were to try to
do the cleanup as a background process, the app would get closed out from under
us. What we really need is a shutdown process that allows us to perform cleanup
and report back to the app framework that we're done.

Comment 3

[Keyser Sose]

So WONTFIX?

Comment 4

[David :Bienvenu]

Oh, no, I think this has to be fixed one day - it's just outside of my control.
It's a big architecture thing, but I've never been able to get cycles from the
people who could do something about it.

Comment 5

[Keyser Sose]

Marking NEW.

Comment 6

[David :Bienvenu]

setting priority

Comment 7

[Nikolay Shopik]

David you still work on this?

Comment 8

[Wayne Mery (:wsmwk)]

assignee=nobody, so >status=new

Comment 10

[Wayne Mery (:wsmwk)]

I don't see a reason to keep this duplicate open