perf tracking bug for mail/news

RESOLVED WORKSFORME

Status

defect
RESOLVED WORKSFORME
19 years ago
5 years ago

People

(Reporter: stephend, Unassigned)

Tracking

(Depends on 2 bugs, {meta, perf})

Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

()

This bug is the tracking bug for mail/news bugs relating to performance.
Depends on: 22486, 22960, 26131, 26456, 47645
Keywords: perf
QA Contact: esther → stephend
Keywords: meta
Descriptions:

Bug 63120 - Real time thread pane scrolling performance is poor
Bug 22486 - Message Reply speed
Bug 22960 - Message Display speed
Bug 26131 - Thread Pane Sorting speed
Bug 47645 - Delete Message speed is slow
Bug 62985 - subscribe tree slow to open "alt." with typedown.
Bug 26456 - Folder loading speed

Keywords: meta
Tnx stephen
Keywords: mozilla1.0
meta bugs can't be nominated.
Keywords: mail3, mozilla1.0, nsbeta1mail1
Says who? It makes perfect sense to me.
(But i just noticed that I nominated the wrong bug.)
Specific, individual bugs are nominated.  What does nominating a meta bug 
mean?  That every bug being tracked is approved?  That doesn't make sense.
I'm marking this nsbeta1-.  You can nominate any bug you want, but this bug is 
too broad to track when it comes time to make decisions about what does or 
doesn't make it as time goes on.  The individual bugs that we care about should 
be tracked.  BTW, at some point in the past there was another performance meta 
bug for mailnews out there. I don't know what happened to it.  
Keywords: nsbeta1-
Bug 49212 - Deleting Messages in a Local Folder causes tons of repainting.
bug 64868 Shouldn't keep open all mail db's
bug 63115 Mozilla chokes with 100 000 new headers to download
Depends on: 63115, 64868
mass accepting my bugs.
Status: NEW → ASSIGNED
Depends on: 87164
Depends on: 101315
Depends on: 35294, 100835
Depends on: 85209, 88449, 89061, 89660, 97713
Depends on: 85029
No longer depends on: 85209
Depends on: 12896
Depends on: 104989
Depends on: 26455
Priority: -- → P3
Target Milestone: --- → Future
Depends on: 117506
Severity: major → normal
Priority: P3 → --
Depends on: 201670
I'm no longer at Netscape/AOL, but I suspect these tracking bugs may be useful
for those still actively involved, as well as future development.

QA and assignee changes -> nobody@mozilla.org
Assignee: stephend → nobody
Status: ASSIGNED → NEW
QA Contact: stephend → nobody
Product: Browser → Seamonkey
Bugs I think should be listed here or are related to the bugs listed here:
bug 64764 - very long list of recipients hangs mozilla for a very long time
bug 152842 - freeze, if i'm reading email in attachment
bug 194709 - expanding long recipient list slow and hogs CPU cycles
bug 210943 - Mozilla is inoperable while it is loading large plain text message
bug 210946 - Large plain text messages are processed VERY slowly
bug 215183 - Program freezes when opening large (over 100K) messages
bug 238440 - large mail freezes ui
bug 242816 - Large message with attachment cannot be opened
Assignee: nobody → mail
QA Contact: nobody → search
Target Milestone: Future → ---
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Long abandoned tracker.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → WORKSFORME
Next best thing is:
Bug 91351 - UI/App responsiveness issues
Assignee: mail → nobody
QA Contact: search → message-display
You need to log in before you can comment on or make changes to this bug.